Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Purpose

Commits Lead to Broken Builds shows the ratio of commits that led to broken builds compared to the total amount of commits at a specific date. Default time depth is 1 month up to the current date. 

How metric helps

It indicates the effectiveness of a code quality quards. The greater this percentage the worse. Metric may help identify build problems as they occur, pointing the source of the error.

How it works

Chart Overview

Chart shows % of commits which led to broken builds - Axis Y per job/pipeline day by day - Axis X. Legend on the top of the chart gives the latest value for each configured job/pipeline.

2017-10-23_17-03-03.png

Calculation Formula

Commits led to broken builds = Ncommit_fail/Ncommit_all * 100 %,

where

Ncommit_fail - number of commits in failed builds

Ncommit_all - number of commits in all builds

Example for a particular date on a timeline: 

Given: total # of all builds on that day5
Given: # of failed builds2
Given: # of commits in all builds15
Given: # of commits in failed builds3
Calculated: Commits led to broken builds %
3 / 15 = 0.2 = 20% = Amber

RAG thresholds: Red > 50%, Amber > 10%, otherwise Green.

Data Source

Data for the metric can be retrieved from Jenkins/GitLab CI. When using Jenkins make sure Git plug in is installed.



  • No labels