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 The default time depth is 1 month up to the current date. Percentage revealed by this metric indicates the effectiveness with which quality guards are controlling the code before it is committed
In order to change the default “time depth” value, you should look at “How many last values to display”(days) in Metric Settings
How metric helps
It indicates the effectiveness of code quality guards. The greater this percentage the worse.
How this metric helps
Metric may help identify build problems as they occur, pointing to the source of the error.
How it works
Chart Overview
Chart The 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 gives the latest value for each configured sub-unit. Sub-units are clickable to display/hide its series on the chart.
Calculation Formula
Here is the example of how metric may be calculated:
job/pipeline.
...
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 day | 5 |
|---|---|
Given: # of failed builds | 2 |
Given: # of commits in all builds | 15 |
Given: # of commits in failed builds | 3 |
Calculated: Commits led to broken builds % | 3 / 15 = 0.2 = 20% = Amber |
|---|
RAG thresholds: Red - metric value > 50%, Amber - metric value > 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.
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|