Jenkins Clover Plugin 4.9.0 has been released RSS

In this release we focused on solving bugs related with Pipeline builds and remote agents.

We fixed JENKINS-45981, JENKINS-33610 and JENKINS-34439 bugs.

We also solved the problem of automatic Clover integration not running on Windows and later Jenkins versions. Integration is now also smarter and does not attempt to integrate with non-Ant tasks.

In addition to this we bumped minimum Jenkins version required to run the plugin. You have to use Jenkins 1.642.3 or higher. Note that this is the minimum version required by the Workflow Plugin 2.0 (aka the Pipelines Plugin).

But we also did not forget to give something to please your eyes :) The 'OpenClover coverage summary' page has better look-and-feel of tables now.

Autumn update

We have documentation!

We are happy to announce that we have prepared end-user and developer documentation on our website. You can enjoy quick start guides, tutorials, plugin-specific guides, knowledge base articles and many many more. It's over 300 pages in total! And this is not a simple copy-and-paste - all code snippets, URLs, Maven artifact IDs etc have been updated to OpenClover. You will no longer have to jump back and forth between and sites and wonder what is different between Clover and OpenClover.

We have new plugin for SBT

Thanks to one volunteer, OpenClover has a second plugin for SBT: This plugin supports newer SBT versions, links with OpenClover and SBT's internal tasks (test in Test, compile in Compile) are used for the build, rather than a custom scope.

OpenClover goes to the Hackengarten

On 18th of October, our project team member, Grzegorz Lewandowski, went to Hackengarten organized by Tricity Java User Group and presented OpenClover. The feedback was very positive and we found 5 volunteers willing to hack and code for us! Unfortunately they did not deliver any feature yet, as most of the time was spent on setting up development environment (it's a lesson for us to be better prepared and to simplify our build processes) and explaining OpenClover details. Nevertheless, the Hackengarten is a cyclic event, so stay tuned! In case you happen to be in GdaƄsk, Poland and would like to join our forces, please watch the for new meetings.

New 4.2.1 release is coming soon

This will be a bug-fix release in which we solve compatibility issues with Maven 2.x. It has also fixes for automatic Ant and Maven integrators, required for CI systems, such as Jenkins or Bamboo. More details on

What's next?

As I wrote in my previous blog post, we want to focus on Gradle and Jenkins plugins. I am also working on better support for OpenClover in Bamboo - so that it will be possible to use automatic integration feature.

OpenClover 4.2.0 has been released. What's next?

This is a cross-post of OpenClover's newsletter.

OpenClover 4.2.0 is available
We are happy to announce that our first release of OpenClover is out. It is based on the open-sourced code of Atlassian Clover 4.1.2. Kudos for Atlassian for open-sourcing it! You can download OpenClover Core as well as integrations for Ant, Maven, Grails, Eclipse, IntelliJ IDEA, Jenkins, Hudson and AspectJ and enjoy the powerful HTML reports.

We're looking for contributors for Gradle Plugin
Unfortunately the Gradle Plugin for OpenClover is not ready yet. We decided to postpone it because does not handle multi-module projects, which we believe is a very common setup. In case you feel confident with writing plugins for Gradle and would like to help us, your contribution will be more than welcome!

What's next?
In the incoming months we're going to:

  • release the Gradle Plugin
  • attack the Jenkins Plugin, which has several critical bugs
  • prepare end-user and developer documentation on our website
Your feedback is valuable, feel free to report issues in our tracker or email us directly.

Welcome to OpenClover

In April 2017 Atlassian® decided to publish sources of Clover - the most sophisticated code coverage tool for Java and Groovy. Clover has been commercially developed for nearly fifteen years (first by Cenqua, next by Atlassian), so literally thousands of man hours were spent on making it so rich in features. Clover's source base is about 10 times larger than second best coverage tool - JaCoCo. I must admit that I had a pleasure to be one of its developers for five years. Thus, as you can notice, making Clover completely free and open source is an amazing gift from Atlassian to the open source community. Great kudos for Atlassian!

Clover is not only rich in features, but also unique compared to other code coverage tools (such as JaCoCo or Cobertura), because it's based on the source code instrumentation (and not the bytecode instrumentation). While this approach has some limitations (you need to recompile the code, for instance) it gives huge benefits, for instance:

  • as Clover "knows" the code structure it can measure 20+ code metrics
  • it can recognize language- or framework-specific code constructs
  • it is more "transparent" to other bytecode manipulating tools

I've been working on Clover since 2012 and I dare to say that several recent major releases of Clover (such as version 3.2 with Java 8, version 3.3 with parameterised JUnit4 and Spock tests or version 4.0 with overhauled HTML report) came out of my hands. I had the opportunity to do everything - from technical support to being developer lead and planning a road map. I know the product inside out and I really love it - from both end-user and a programmer perspective (the code is really solid piece of work). So at the moment I heard about the idea of open-sourcing it, I immediately knew that I want to participate in this "new life" of Clover.

So here we are: a new home page you're reading right now is set up, all sources are available for download from Bitbucket, I am working on a binary release of OpenClover 4.2, which should be ready quite soon. I am eager to share my expertize and to coordinate the entire open source project.

You may ask: What can I do?

My answer is: Just start using it! I am certain that you'll love it! Spread the word, ask questions, provide answers on Q&A forums like Atlassian Answers or Stackoverflow. Migrate your builds from Clover 4.1 (or older) to OpenClover 4.2 as soon as it becomes available.

The bigger user base, the bigger active Clover community, the bigger chance to find new volunteers to contribute to Clover. And last but not least the bigger motivation for me :-) to drive the whole project.

Or maybe you would like to contribute? If yes, then jump to the Clover Development Hub for build instructions, clone the repository and grab some bug or feature request for implementation.

I am looking forward to hear from you. You can catch me via email

Subscribe to our newsletter

Get notified about new releases and other news. Don't worry about spam, we will send one mail per month at most.