This plugin requires Jenkins 1.509 or better and the Global Build Stats plugin 1.2 or better.
To install the build metrics plugin, Go to "Manage Jenkins" -> "Plugin Management". Check the latest version and install. You will probably need to restart the Jenkins server after that.
Go to "Manage Jenkins". You should see an icon of Jenkins with a little data grid in front. Click that and it will take you to the Built Metrics Search screen (see below).
The search screen is where you tell the plugin which jobs you wish to report on and what timeframe should be included in the report.
Configure the following parameters:
Click Search and the report will be generated and displayed (see Build Metrics Report Screen below)
The build metrics report screen is split into two sections. The top section contains the selected jobs and their associated build metrics. The bottom section contains a list of failed builds; complete with the job name, a link to the console output of the build, and a link to the build itself as well as a section to display the 'cause' for the build (see description of adding build failure cause below).
I found it useful to have a description in the report for why the build failed. This way I could see trends as they happened over time. To add a cause:
This plugin was created because the team I work on needed to deliver some concise build metrics for our Jenkins builds on a rolling two week iteration. These build metrics needed to have an overall failure rate and an individual one per job, as well as a list of failed builds (with associated causes). This plugin provides that reporting mechanism. To be really useful though, we needed to be able to pull it up quickly and easily every time we wanted to generate the report. I use the sidebar links plugin to accomplish this, by simply copying the url for the build metrics report screen for a given set of search criteria. I then enter this URL as a sidebar link, using the icon that I created for the plugin and the description (1st parameter on the search page) as the txt of the link. This way all of our users can just go to the main Jenkins dashboard and pull up the report as needed.
We currently take the results of the report, copy them into an email and send that to our development teams as a 'report card'. A great next-step for the use of this plugin would be to have a job that ran the report and emailed out the contents on a scheduled basis.