View Clover on the plugin site for more information.
This plugin allows you to capture code coverage reports from Clover. Jenkins will generate and track code coverage across time. This plugin can be used without the need to modify your build.xml.
Automatic integration for Ant builds
Since version 2.0 of the Clover Plugin, Clover can be integrated into Ant-based builds without the need to modify the build.xml . Simply check the "Automatically record and report Code Coverage" checkbox in the Job configuration screen.
The Clover plugin will add an Ant build listener and appropriate configuration parameters to allow Clover HTML, XML, JSON and Historical reports to be generated for your Job.
These will automatically be linked to from the Job and Build pages.
The Clover License string can be configured either per-Job, or globally view the "Manage Jenkins -> Configure System -> Manage Clover" screen.
It works for typical build configurations in which unit tests are launched after compilation. In case you spawn processes, run in-container tests, deploy application to another machine etc then the automatic integration will not be sufficient and you'll have to set up integration manually.
We recommend reading the official Clover Documentation home page - you will find instructions how to integrate Clover with Ant, Maven, Grails and other tools.
In case of trouble, you may have a look at the Atlassian Answers page (questions tagged 'clover').
Manually configuring the Clover plugin
- Install the Clover plugin
- Configure your project's build script to generate Clover XML reports
- Optional: Configure your project's build script to generate clover HTML or PDF reports (this plugin prefers HTML reports to PDF). The plugin will not extract any information from these reports, but will use them as a better formatted most recent coverage report when they are available.
- Enable the "Publish Clover Coverage Report" publisher
- Specify the directory where the clover.xml report is generated.
- Optional: Configure the coverage metric targets to reflect your goals.
Maven configuration with freestyle project
The clover-maven-plugin is one of the plugins that highlights an issue with how Maven 2 handles aggregator goals.
Jenkins cannot handle maven aggregator goals with the maven2 project (alpha) project type due to how this project type calls Maven. In order to obtain multi-module clover reports, you must therefore use the free-style software project project type. In any case, the Jenkins Clover Plugin does not currently support the maven2 project (alpha) project type. In order to ensure that the correct aggregated report is generated, it is necessary to invoke maven multiple times.
- Create the job as a "free-style software project".
- Enable the "Invoke top-level Maven targets" Build.
- Specify the following goals for Maven: (Note the use of the pipe character | to invoke maven three times).
- Enable the "Publish Clover Coverage Report" publisher.
- Depending on your Source Code Management, the clover report directory will either be "target/site/clover" or "module-name/target/site/clover"
- Don't forget to configure the pom.xml to generate the clover.xml report
Maven2, Clover and Multimodule with a <packaging>ear</packaging> child module
The maven2 ear packaging will break if you use the clover goal at any time during the same invokation of maven if you ivoke the package or later phases (as it will see artifacts without a classifier and with the clover classifier, get confused and give up)
To work around this, you should configurer your root pom to include the <packaging>ear</packaging> targets only when you are not using clover... how to do this:
The above... hack... is why it is recommended to invoke maven three times. If you don't need this hack, you could simplify down to two invocations and specify the clover license file location in the pom.xml, i.e. install clover:instrument | -N clover:aggregate clove:site
Version 4.4.0 (July 18, 2014)
- Upgrade to new major Clover release which is 4.0.0. This release comes with a completely redesigned HTML report, following the ADG (Atlassian Design Guidelines).
Version 4.3.0 (April 1, 2014)
- Upgrade to new major Clover release which is 3.3.0. This release comes with a dedicated support for Spock framework JUnit4 parameterized tests.
Version 4.2.0 (October 23, 2013)
- Upgrade to new major Clover release which is 3.2.0. This release supports instrumentation of Java 8 language.
Version 4.1.0 (August 13, 2012)
- Upgrade to Clover 126.96.36.199
Version 4.0.6 (May 13, 2012)
- Upgrade to Clover 3.1.5
Version 4.0.5 (Jan 18, 2012)
- Upgrade to Clover 3.1.3 (JENKINS-12448).
Version 4.0.4 (Nov 8, 2011)
- Upgrade to Clover 3.1.2 (JENKINS-11656).
Version 4.0.2 (Jun 6, 2011)
- Upgrade to Clover 3.1.0 (JENKINS-9830).
Version 4.0.1 (May 7, 2011)
- Clover plugin uses HTML in display name (JENKINS-9435).
- Jenkins 1.399 or later
- fixed the icon path on configuration pages (JENKINS-7795).
- Clover Coverage Trend Report Stop Displaying For Failed Build (JENKINS-3918).
- Ignore 0/0 Conditional in coverage graph (JENKINS-8198).
- i18n & i10n(ja)
- Fixed NoStaplerConstructorException with recent Jenkins versions.
- Update to Clover 3.0.2.
- Upgrade to Clover 3.0 which has Support for Groovy
- View Release Notes
- No other changes to the Hudson Clover plugin, apart from its dependency on Clover 3.0