Purpose

This chart shows Build Results shows the distribution of builds by status (success, fail, abort, and few more) on a daily basis within 1 month up to the current day. Ideal target for this chart is all success (means no failures) for each day. 

How this metric helps

...

This not necessarily a "metric" (as it can hardly be represented as a single number), but rather a chart.

Build failures might happen from time to time. Monitoring of those failures vs. overall picture will help immature teams and processes to evolve and introduce stronger quality guards for the committed code - thus increasing the efficiency of a whole delivery pipeline. By tracking failures, we summarized on this chart, you can quickly identify the changes that led to the a failure and resolve them more quickly than we could otherwise. And not only for responding to problems may this metric be helpful. then target improvements within a process more efficiently. In a wider sense it , this chart shows how healthy your CD a build/Ci/Cd process is, and how effective your developers are at resolving and preventing failures.

May become The metric is extremely helpful on at a stabilization phase of a project/release when no active development but rather bug fixing is supposedtakes place.

How it works

Chart Overview

Chart displays the ratio a number of builds by status (Axis Y) on day-by-day timeline (Axis X). Legend on the top shows the number of builds resulted in success, failure or any other status for the current day and also deciphers build status coloring applied for the chart.Image Removed

...

Calculation Formula

Metric calculates the total number At the chart a count of builds and divide those by statuses by status is shown for each day.

Data Source

Data for the metric may be collected from Jenkins/GitLab CI.