Build Failure Analyzer

compared with
Current by Robert Sandell
on Apr 01, 2014 12:58.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (7)

View Page History
Plugin developers can add new Indication types and more are planned to be added to the plugin itself.
The Build Log Indication searches through the build log, one line at a time, for a regular expression.
It uses Pattern.match, so the regular expression needs to match the whole line, e.g. \*.*some .\**some words in the middle of a line.\**

_Adding new failure causes and indications to the knowledge base._

From version 1.3.1 of the plugin, regular expressions can be tested on the Failure Cause Management page, in two different ways:

* Writing a text in the text field shown above and testing against that.
* Writing a URL to a build log in the text field. The plugin then runs through the log trying to match the regexp.

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:
* Local knowledge base. Saves the knowledge base in memory and serializes it as an xml file on the local Jenkins server (i.e. the "standard" Jenkins way of saving information).
h3. Statistics

If MongoDB or some knowledge base type that supports MongoDB statistics is used, statistics will be saved to that database. The same information
that is shown on the build page is saved to the database.

* Concurrent scans - To speed up the scanning, each build will get a threadpool of this number of threads, with each thread handling one indication. For a small system, 3 is usually enough.

h2. Tips & Tricks

h3. Aggregate statistics to Graphite

If you are using the MongoDB KnowledgeBase, you can use these scripts in a cron job to aggregate the statistics into Graphite.

* [Known vs. Unknown Failures per hour|]
* [Failure Categories per hour|]

h2. Change Log

h4. Version 1.7.0 (released Apr 1, 2014)

* Multi line build log indications
* Optionally store statistics about successful builds

h4. Version 1.6.0 (released Mar 10, 2014)

* Ability to re-scan non scanned builds (for new installations) and all builds for a project
* Graphs on projects, slaves and master(s) if using a statistics logging enabled knowledge base (like the MongoDB Knowledge base)
* Shows failure causes from downstream builds directly on the upstream build page.
* ListView column showing the failure cause of the last build, if there is one.

h4. Version 1.5.1 (released Nov 19, 2013)

* Fixed an XSS vulnerability

h4. Version 1.5.0 (released Apr 24, 2013)

h5. New Features

* The found failure cause is exposed to the REST Api (jobX/1/api).

h4. Version 1.4.1 (released Mar 14, 2013)

h5. Bugs fixed

* [JENKINS-16868|] Icons are not displayed with a reverse proxy

h4. Version 1.4.0 (released Feb 15, 2013)

h5. New Features

* Possibility to test regexps on a build log

h5. Bugs fixed

* Log annotation bugfixes.
* [JENKINS-15948|] Build Failure Analyzer icons aren't displayed if Jenkins isn't installed at root context.(again)
* [JENKINS-15926|] Build Failure Analyzer with Timestamper output ugly.(again)
* [JENKINS-16596|] Repeat/double loggin issue due to Build failure Analyzer.
* [JENKINS-16104|] Build Failure Analyzer: Ugly output from plugin.
* NPE fix when a slave is taken offline during a build.
* Fix for internal serialization of matrix aggregated indications.
* Small UI fix in failure cause management page.

h4. Version 1.3.0 (released Dec 06, 2012)

h5. New Features

* Possibility to test regexp on a line of text when editing BuildLogIndications
* Output from Build Failure Analyzer shown in normal console.

h5. Bugs fixed

* [JENKINS-15986|] Cannot save job configuration pages on Jenkins 1.463 or newer.
* [JENKINS-15948|] Build Failure Analyzer icons aren't displayed if Jenkins isn't installed at root context.
* [JENKINS-15926|] Build Failure Analyzer with Timestamper output ugly.

h5. Other

* Updated Gerrit Trigger optional dependency: 2.7.0

h4. Version 1.2.0 (released Nov 22, 2012)