{jenkins-plugin-info:pluginId=global-build-stats}
Global build stats plugin will allow to gather and display global build result statistics.
It is a useful tool allowing to display global jenkins/hudson build trend over time.

Requirements

Since v1.1, Global build stats plugin requires Jenkins 1.398 or higher.

Before v1.0, Global build stats plugin requires Jenkins/Hudson 1.339 or higher.

Installation

To install Global build stats Plugin, Go to the "plugin management" section in the administration Panel.
Latest released version will be available. Install it from there (you should need to restart Jenkins/Hudson after that).

To verify that the plugin is well installed, go to the Administration panel : you should see an icon with mister Jenkins/Hudson and a graph on it :
 or 

Then you can click it and access the global build stats config panel.

Usage

The global build stats main screen is made of different sections :

Action links

4 links are availables :

Data Initialization

If you click on this button, all of your existing persisted build results will be gathered.
This is particularly useful to initialize statistics in a first step.
Note that data initialization gathering is only based on "recordable" data. If you frequently purged your job results, data will no longer be available for gathering. Nevertheless, once data has been initialized in global-build-stats, it will be made available even if data is purged (result data is cloned in the global-build-stats.xml file).
Starting from 0.1 (and greater ones), you can perform several data initializations : existing global-build-stats.xml will be merged against eventually new gathered data.

Take into account the following only if you are using a 0.1-alphaX version of global-build-stats plugin (for greater versions, data are merged and thus, never lost) :
Beware : this should be done only once because :

Manage retention strategies

This section is for customizing job build result retention for global-build-stats plugin.
Job build result is the largest data stored in global build stats configuration files (in global-build-stats.xml or global-build-stats/jobResults/*). That is to say, if you're expecting some disk consumption issue, a workaround would be to be stricter on the job build result retention strategies.

Using retention strategies will delete permanently job build results. Thus, you won't be able to retrieve them.
Take this functionality with care.

Prior to version 1.2, 3 retention strategies are available :

Build stats Chart Creation / Update

In this popup form, you can create a new Build Stats Chart.

Here are some details on the different parameters :

All fields are mandatory. Chart's width, height & length should be integers.
If at least 1 server-side validation fails, form will not be "submittable".

Before submitting the form, you can have a look at the future chart which will be displayed by clicking the "overview" button.

Build stats Chart display

This section displays every persisted Chart Configurations.
You can, too, edit, delete or move up/down these graphs.
Graphs are created using REST-like URL so that you can export this URLs into your favourite Portal or CMS (or Jenkins/Hudson dashboard).
2 chart examples can be seen below :

Last chart displays the 3 available dimensions altogether (result counts, total build time & average build time).

By clicking a results counts region, you will be redirected on the build search engine screen.
See the Build Search engine section for further details.

Near every build chart, you'll have at least two button : edit & delete buttons.
Depending of the placement of your chart, you'll be able to "move up/down" the chart.

Notes about user & node filtering

Don't expect to have relevant results just after an upgrade between :

  • pre and post 0.4 versions for node filtering
  • pre and post 1.0 versions for user filtering

When migrating, only not purged data (concerning node & user having launched the build) will be recorded.
That is, "old" data (such as builds executed a few weeks ago) won't be available.

Starting from your plugin upgrade, full data will obviously be recorded.

Notes about durations displayed when migrating to v0.5

For the same reasons as above, don't expect to have relevant results just after an upgrade between pre and post 0.5 versions : you'll have to wait a few times in order to have sufficient data amount to calculate total & average build duration.

Build search engine

The build search engine is accessible by clicking a build result region on a chart.
It will provide search criteria to query the global-build-stats build results on different ways : result status, job name, node name and date ranges.

Result sort order can be changed by clicking the table headers.
If build result has not been purged, a clickable link will be displayed to navigate through the console output & the detailed build result.

Bonus track : Global-build-stats JSON API

A detailed section has been created to describe how to retrieve global-build-stats data from Jenkins/Hudson standard JSON & REST API.

Product backlog

Known issues

Future version(s)

Identified issues :
JENKINS-7241: Special characters in chart title ("é" for example) are not well filling textfields in edit form
Fix legend item sorting (for now, sort depends on alphabetical order... that's why statuses are prefixed with "1), 2).."
Fix date displayed on build search view, due to yui calendars
Rename persisted node names in global-build-stats.xml after node is renamed

Features :
Test global build stat behaviour under IE & Safari
Cache chart renderings (provide a checkbox in the buildStatConfiguration, allowing to enable chart caching with a given refresh rate based on selected time scale). Chart rendering will cache chart in-memory (thus it will consume a little bit more memory) but will reduce the CPU used when displaying the chart. It feets particularly well if you decide to "share" your chart with lots of users that will want to display it (on the jenkins/hudson welcome screen for example)
In build search results, allow to limit number of results (radio button allowing "unlimited" and "limited to XXX results")
Allow to select build start or build end for stats gathering (build end could be calculated with build start + duration). For now, we use only build start
(if possible) Allow to click on a date to display date builds (no matter the build result)
If possible, provide tooltips on chart, displaying the 10 first job names matching with the current hovered region

Tasks :

Releases

1.5 (October 23, 2017)

1.3 (April, 5th, 2012)

Improvements

1.2 (August, 25th, 2011)

Improvements

Bugs

1.1 (August, 3rd, 2011)

Tasks

1.0 (November, 14th, 2010)

Fixed bugs

Improvements

Tasks

0.5 (September, 23th, 2010)

Improvements

0.4.1 (September, 16th, 2010)

Fixed bugs

0.4 (September, 15th, 2010)

Fixed bugs

Improvements

Tasks

0.3.1 (August, 18th, 2010)

Fixed bugs

0.3 (August, 17th, 2010)

Fixed bugs

Improvements

Tasks

0.2 (July, 4th, 2010)

Fixed bugs

Improvements

0.1 (June, 13th, 2010)

Fixed bugs

Improvements

0.1-alpha4 (March, 13th, 2010)

AJAX Form validation enabled

0.1-alpha3 (March, 1st, 2010)

Fixed bug : If checkbox are unchecked, build stat config is not added
Some precision : if chart doesn't appear after form submission, check your fields : all are mandatory (except for checkboxes which can be unchecked), width & heigth & length should be integers

0.1-alpha2 (March, 1st, 2010)

Minimum Jenkins/Hudson version downgraded from 1.339 to 1.321
Chart persistence implemented.
Create/Update/Delete multiple chart build configurations.
Added job name filtering.
Changed displayed date pattern on chart.
Server-side form validation is done .... but nothing is displayed on the user side (due of lack on knowledge on form validation ... see 0.1 roadmap to see how this will be handled in the future)

0.1-alpha1 (February, 21th, 2010)

First release.
Contained only a unique chart and the possibility to initialize build stats from existing build results.
Chart is contructed in a RESTly way that is to say you can provide GEt parameters to the chart.
No Chart persistence implemented.

Greetings to our sponsors

I'm a proud user of .
Feel free to download and test this IDE, it's worth a try !