This plugin analyzes the causes of failed builds and presents the causes on the build page. It does this by using a knowledge base of build failure causes that is built up from scratch.
The plugin comes with an empty knowledge base of failure causes. Populating this knowledge base is done by using the link "Failure Cause Management".
One or more optional categories can be added as a whitespace-separated list. These categories are only used for the statistics part of the plugin.
From version 1.3.1 of the plugin, regular expressions can be tested on the Failure Cause Management page, in two different ways:
When accessing the Failure Cause Management page from a build, the URL will be added to the text field automatically.
The plugin comes with two ways of saving the knowledge base:
All builds on the server that are non-successful (aborted, failed, unstable) will be scanned for all failure causes.
If MongoDB or some knowledge base type that supports statistics is used, statistics will be saved to that database. The same information
On the configure system page in Jenkins, under Build failure analyzer, some new settings are available:
If you are using the MongoDB KnowledgeBase, you can use these scripts in a cron job to aggregate the statistics into Graphite.
Breaks Job configuration pages on Jenkins 1.463 or newer
Skip to end of metadata Go to start of metadata