Purpose

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

How metric helps

Commits Lead to Broken Builds indicates the effectiveness with which quality guards are controlling the code before it is committedof a code quality quards. The greater this percentage the worse.

How this metric helps

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 per sub-unit - Axis Y per job/pipeline day by day - Axis X. Legend placed on the top of the chart delivers latest value for each configured sub-unit. Sub-units are clickable to display/hide its series on the chartjob/pipeline.

Image Modified

Calculation Formula

Here is the example of how metric may be calculatedCommits led to broken builds = N_{commit_fail}/N_{commit_all} * 100 %,

where

N_{commit_fail} - number of commits in failed builds

N_{commit_all} - number of commits in all builds

Example:

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

Data Source

Data for the metric can be retrieved from Jenkins/GITLab CI.