Documentation for Bamboo 4.0.x. Documentation for earlier versions of Bamboo is available too.

Enabling the Clover plugin

Created by Edwin Dawson [Atlassian Technical Writer], last updated by paulwatson on May 02, 2012 1 minute read

This page contains instructions on enabling and configuring the Atlassian Clover plugin for a job in Bamboo.

To enable the Clover plugin on a job:

Navigate to the desired job, as described on Configuring jobs.
Choose Actions > Configure Job.
Click Miscellaneous.
Select Use Clover to collect Code Coverage for this build and complete the following settings:

Related pages:

Setting	Description
Automatically integrate Clover into this build	You will need to provide a Clover license (evaluation licenses are available), unless this has been configured globally in the Administration panel (Administration > Plugins > Clover Plugin).
Generate a Clover Historical Report	Displays the current coverage results compared with previous Clover code coverage reports.
Generate a JSON report	Provides the Clover results in a format ready for embedding into applications or external report views.
Use plan-defined Clover license key	Override the global Clover license for this particular plan.
Clover is already integrated into this build	Use this option when you already have Clover-for-Ant or Clover-for-Maven configured to generate a report.
Clover XML Location	Specify the location where Bamboo will look for the XML report file from Clover. Please specify the file path relative to your plan's root directory (e.g `/home/bamboouser/bamboo-home/xml-data/build-dir/MY_PLAN/`), i.e. do not specify an absolute path. target/site/clover/clover.xml

Screenshot: Enabling Clover for a job

8 Comments

Anonymous
May 09, 2011
When I choose "Automatically integrate Clover..." and my Maven2 goals are just clean and test (ie mvn clean test) bamboo decides that instead it will run (clean test clean clover2:setup verify)

And the problem is that my build server is currently behind a firewall, and is not available for our selenium server to access, so "verify" will always hang. But I dont want verify to run!

How can I integrate clover, but not have Bamboo decide it will run Verify anyway???
1. Anonymous
  Aug 16, 2011
  Just disable automatic clover integration and add the appropriate goals to your Maven task command line. For example, add "clean clover2:setup test".
Anonymous
Aug 04, 2011
'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.

That example is an absolute path.
Anonymous
Oct 18, 2011
This doesn't seem to line up with Bamboo 3.3 at all. There is no Configuration tab once on the plan configuration page..
1. Anonymous
  Oct 18, 2011
  It's now located on any "job" configuration > miscellaneous
  Navigate from plan > stages > default stage > default job
Jim Bethancourt
Nov 09, 2011
Is the Clover plugin / integration available for Atlassian OnDemand?

Thanks,
Jim
dushan abeyruwan
Dec 16, 2011
Hi I enabled clover coverage but I CAN NOT see detail dashbord getting exported to the clover coverage it has view just few details like Test Coverage/ Build Statistics getting displyed,(I found out that detail dashboard details are at target/site/clover/***)
how can I enable my plan to export this dashboard...(I have tried "clover is already integrated ......" option) ? why this is soo buggy
1. Greg Arakelian
  Jan 05, 2012
  I'm having the same problem. Did you ever resolve this?