This plugin reads the "crappy methods" report from Crap4J. Jenkins will generate the trend report of crap percentage and provide detailed information about changes.

Users will be able to track which methods are crappy and when they entered and left the code base.


Currently, this plugin is restricted to use with freestyle (ant) jobs. Future releases might support all kinds of jobs. Let me know your needs by filing a request for enhancement in the issue tracker.


The crap4j plugin scans the Crap4J report data and reports trends.
These features are currently implemented:

Configuring the Crap4J Plugin

  1. Get the crap4j plugin, preferably using Jenkins plugin manager
  2. Install the crap4j plugin in your Jenkins, if downloaded manually
  3. Configure your project's build script to generate crap4j XML reports (This happens along with the HTML report)
  4. Enable the "Publish Crap" publisher on the job configuration page
  5. Specify the directory where the crap4j report (report.xml) is generated
  6. Perform some builds to receive a trend

The crap4j plugin currently has no configurable parameters. The build health indicator is set to the Crap4J quality suggestion, with 15% crappy methods being 0% build health.


This plugin is developed and maintained by Daniel Lindner with kind support from Softwareschneiderei GmbH. Please feel free to contact me for feedback. If you have suggestions for new features or you've found a bug, please use the issue tracker or the mailing lists. If you use the issue tracker, assign the issue directly to java.net ID dlindner.


Release 0.9 (2014-10-22):

Release 0.8 (2010-08-01):

Release 0.7 (2009-12-30):

Release 0.6.1 (2009-03-15):

Release 0.6 (2009-02-25):

Release 0.5 (2008-12-31):

Release 0.4 (2008-07-03):

Release 0.3 (2008-07-03) - please use 0.4 instead.

Release 0.2 (2008-06-03):

Release 0.1 (2008-05-17):