Jenkins Clover Plugin Developer Guide


  • You have GitHub account with SSH keys configured and the local SSH key is not protected by password (otherwise release:prepare will hang)
  • Configure in settings.xml:

    <!-- user/password of your Jenkins account -->
  • Clone the repository from GitHub using SSH:

    git clone jenkins-clover-plugin
  • You have JDK1.6+ installed
  • You have Maven 3.0.5+ installed

Build and test

  1. If you have already cloned jenkinsci/clover-plugin then ensure you git pull upstream

  2. Create a JIRA on for the issue you are fixing.
  3. Make changes necessary. Use issue key in commit messages.
  4. Bump the dependency version of Clover Core if necessary (in pom.xml)
  5. Test by running Jenkins with the Clover plugin installed and setting up a "Clovered" project for CI. This can be achieved via:
    mvn clean hpi:run
    1. it will start Jenkins on localhost:8080 by default, open it in web browser
    2. open "Manage Jenkins" > "Manage plugins" > "Installed" and check if new "Jenkins Clover Plugin" is listed
    3. configure new project (you can use MoneyBags as a test case) and a build job (e.g. "freestyle project" with "ant task")
    4. configure "Post-build actions" > "Publish Clover Coverage Report" in the build job
    5. run "Build now" and check if Clover summary report is available
  6. Commit changes and push to GitHub. Include your JIRA issue from above.

Release and publish

Run release:prepare and release:perform in one command:

mvn release:prepare release:perform

Verify that the plugin has been deployed:


Update the page.


Problem with 'git clone' on Windows

See and how to set it up.

The 'git push' during mvn 'release:prepare' hangs

Probably it hangs on ssh due to id_rsa key protected by a password.


最終更新日: 2016 年 10 月 24 日


Powered by Confluence and Scroll Viewport.