Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Build failures are inevitable, especially when multiple builds are generated in a single day. By tracking failures, we you can quickly identify the changes that led to the failure and resolve them more quickly than we could otherwise. And not only for responding to problems may this metric be helpful. In a wider sense it the metric shows how healthy your CD a deployment 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.

2018-06-04_10-39-37.pngImage Modified

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.