Enabling the Clover add-on

Enable the Clover add-on

1. Navigate to the desired job, as described on Configuring jobs.
2. Choose Actions > Configure Job.
3. Click the Miscellaneous tab.

4. Select Use Clover to collect Code Coverage for this build and complete the following settings:

 target/site/clover/clover.xml 

Screenshot: Settings to enable Clover for a job

Automatic Clover integration

Automatic integration works with Ant, Maven 2.x, Maven 3.x and Grails tasks:

1. Check Use Clover to collect Code Coverage for this build in the Clover Code Coverage settings.
2. Select Automatically integrate Clover into this build.
3. Enter the global license key for Clover (go to Administration > Plugins > Clover Plugin), or enable Use plan-defined Clover license key and paste the key into the text field that appears.

Additionally, you can:

• Select Generate a Clover Historical Report to compare the current coverage results with previous Clover code coverage reports.
• Select Generate a JSON report to get the Clover results in a format ready for embedding into applications or external report views.

Manual Clover integration

Manual Clover integration works with any kind of task in which Clover can be called (Ant, Maven 2.x, Maven 3.x, Command, Grails):

1. Check Use Clover to collect Code Coverage for this build, in the Clover Code Coverage settings.
2. Check Clover is already integrated into this build ...
3. Specify in Clover XML Location where Bamboo will look for the XML report file generated by Clover.

4. On the 'Artifacts' tab, click Create Definition and complete the form as follows:
   
   

   Name	This should begin with with "Clover Report".
   Location	This should point to the HTML report directory (e.g. target/site/clover)
   Copy Pattern	Use **/*.*

   

5. Configure Clover in your build script so that it generates both XML and HTML reports.

   Ant:

   <clover-report initstring="target/clover/database/clover.db">			
       <current outfile="target/site/clover/clover.xml" />
       <current outfile="target/site/clover">
           <format type="html"/>
       </current>
   </clover-report>

   Maven:

   <plugin>
       <groupId>com.atlassian.maven.plugins</groupId>
       <artifactId>maven-clover2-plugin</artifactId>
       <configuration>
           <generateHtml>true</generateHtml>
           <generateXml>true</generateXml>
       </configuration>
   </plugin>

6. Configure the Clover license in your build script or pass it as a proper task parameter in the job configuration:
   

   1. Save the Clover license key in a file (for example in /opt/bamboo/clover.license).
   2. Pass the location of the license key to the build task:
      • Define it in the build script, or
      • Pass it as a Java property for the Ant/Maven task in the plan configuration.

   
   Example - declare license location in pom.xml (Maven)
   

   <plugin>
       <groupId>com.atlassian.maven.plugins</groupId>
       <artifactId>maven-clover2-plugin</artifactId>
       <version>3.1.8</version>
       <configuration>
           <licenseLocation>/opt/bamboo/clover.license</licenseLocation>
           <generateXml>true</generateXml>
           <generateHtml>true</generateHtml>
       </configuration>
   </plugin>

   
   

   Example - declare license location in build.xml (Ant)

   <project>
     <property name="clover.license.path" location="/opt/bamboo/clover.license"/>
     <!-- ... -->
   </project>

   
   

   Example - pass license location for Ant task:

   clean with.clover test clover.report -Dclover.license.path=/opt/bamboo/clover.license

   
   

   Example - pass license location for Maven task:

   mvn clean clover2:setup verify clover2:aggregate clover2:clover -Dmaven.clover.licenseLocation=/opt/bamboo/clover.license

    

   

    

After every build, Bamboo will parse the Clover XML file and generate statistics and charts for a plan summary. The Plan summary and job summary pages will contain a "Clover" tab. 

Browsing Clover results

Clover HTML report and Clover statistics for a job: see Viewing the Clover code-coverage for a plan. 

Clover code coverage summary for a plan: see Viewing the Clover code-coverage for a build.

Clover code coverage statistics across multiple plans: see Generating reports across multiple plans.

Limit the machines that Clover runs on

Troubleshooting

Automatic or manual Clover integration and spawned processes

Using automatic Clover integration or adding a dependency to the maven-clover2-plugin manually is usually sufficient.

However, if your build spawns another JVM process (for example: unit tests executed in a forked JVM, tests in the container instantiated on the fly, tests calling code deployed on another server), you must manually add the dependency to the Clover JAR for these spawned processes.

See NoClassDefFoundError com_atlassian_clover/CoverageRecorder KB article.

Automatic Clover integration and building in a subdirectory

In case you perform a build in a subdirectory (for instance, in the Maven Task configuration you have the "Working sub directory" field set) and you have automatic Clover integration, you may need to correct the Location in the "Clover Report (System)" artifact. Otherwise, an HTML report may be empty as automatic Clover integration uses the default path (for instance, the "target/site/clover" in case of integration with Maven). This bug has been fixed in Bamboo 5.7.

Automatic Clover integration and multi-module Maven projects

If you have a multi-module Maven project with dependencies between modules and use Automatic Clover integration, it can happen that an instrumented JAR of the dependent artifact will be taken for test execution in a build phase where Clover was not enabled yet. See BAM-13208 for more details. In such case, we recommend the following:

• create a separate Job in which automatic Clover integration is enabled
• create a Maven task in this job, which will do nothing (call the "clean" goal, for instance)
• Bamboo will automatically add Clover-related goals (clover2:setup verify clover2:aggregate clover2:clover)