_planBuilderCommonOptions

Update the following general build parameters:

• 'The build will produce test results' — Select this check-box if you want Bamboo to gather test results data for each build result. (Note that Bamboo requires test results to be XML files that are compatible with JUnit XML format. This format is also used by TestNG):
  • 'Look in the standard test results directory' — Select this option if Bamboo should look in the Builder's standard test results directory.
  • 'Specify custom results directories' — Select this option if the Builder will place generated test results in an alternative directory. The following field will appear:
    • 'Specify custom results directories' — Type the name of the test results directory (or multiple directories, separated by commas). You can also use Ant-style patterns such as */test-reports/.xml. Please specify file path relative to your plan's root directory (e.g /home/bamboouser/bamboo-home/xml-data/build-dir/MY_PLAN/), i.e. please do not specify an absolute path.
• 'NCover output will be produced' — Do not check this option. NCover is not relevant to Ant builders.
• 'Override default build hanging detection' — Select this check-box if you want to override the default build hanging detection settings. These settings determine when a build hung event is thrown (e.g. you can configure your notifications to trigger from this event). The following settings will be displayed:
  • 'Build Time Multiplier' — This setting is used to calculate the 'Expected Build Time' for the build, i.e. 'Expected Build Time' = 'Build Time Multiplier' times 'Average Build Time' (note, the 'Average Build Time' is calculated by Bamboo by using an average of previous build times)
  • 'Log Quiet Time' — This is the amount of time since Bamboo last recorded an entry in the build log for a build.
    The 'Expected Build Time' and 'Log Quiet Time' must both be exceeded for Bamboo to throw the build hung event.
  • 'Build Queue Timeout' — This is the amount of time that a build will wait in a build queue before an timeout event is thrown. Setting this value will override the global build queue timeout setting (see Configuring the Build Queue Timeout Event).
• 'Use Clover to collect Code Coverage for this build.' — Select this check-box if you are running Atlassian Clover and want to collect code-coverage data to view from within Bamboo (see Viewing the Clover Code-Coverage for a Build Result). The following fields will be displayed:
  • 'Integration Options' — Select one of the following options:
    • 'Automatically integrate Clover into this build' — For this option, you have two sub options; 'Generate a Clover Historical Report' and 'Generate a JSON report'. The Clover Historical Report shows the current coverage results compared with previous Clover code coverage reports. The JSON report gives the Clover results in a format ready for embedding into applications or external report views.
      You will also need to insert a Clover license (evaluation licenses are available) into the field provided.
      A issue currently exists preventing this option working on Windows. Please see Enabling the Clover Plugin for more information.
    • 'Clover is already integrated into this build and a clover.xml file will be produced' — Use this option when you already have Clover-for-Ant or Clover-for-Maven configured to generate a report. You will also need to specify where the Clover XML report is being generated, under 'Clover XML Location'. For this, specify the name of the directory (including path) where Bamboo will look for the XML report output file from Clover. Please specify a file path relative to your plan's root directory, for example:

       target/site/clover/clover.xml 

      Do not specify an absolute path.
  • 'Clover XML Location' — Specify the location where Bamboo will look for the XML report output file from Clover. Please specify file path relative to your plan's root directory (e.g /home/bamboouser/bamboo-home/xml-data/build-dir/MY_PLAN/), i.e. please do not specify an absolute path.