This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

  • '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). If selected, the following options will appear:
    • 'Build Time Multiplier' — This setting is used to calculate the 'Expected Build Time' for the build (i.e. 'Expected Build Time' = 'Build Time Multiplier' multiplied by 'Average Build Time').
      (info) 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.
      (info) 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 Job Build Queue Timeout Event).
  • 'NCover output will be produced' — Do not select this option. NCover is a code coverage tool that supports .NET projects.
  • 'Use Clover to collect Code Coverage for this build' — Select this check box if:
    • This Job will be building a Java-/Groovy-based project using a builder such as Ant, Maven or Grails.
    • 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).
      If you select this check box, you can specify one of the following Clover 'Integration 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.
        (info) 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 Job build's root directory, for example: 
        target/site/clover/clover.xml
        (warning) Do not specify an absolute path.
  • ラベルなし





Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.