Build Count

What is this metric?

The number of successful builds.

Why is it important?

1. As a process indicator, it reflects the value flow efficiency of upstream production and research links
2. Identify excellent/to-be-improved practices that impact the build, and drive the team to precipitate reusable tools and mechanisms to build infrastructure for fast and high-frequency delivery

Which dashboard(s) does it exist in

• Jenkins

How is it calculated?

This metric is calculated by counting the number of successful cicd_pipelines, such as Jenkins builds, GitLab pipelines and GitHub workflow runs in the given data range.

Data Sources Required

This metric relies on Jenkins builds, GitLab pipelines or GitHub workflow runs.

Data Transformation Required

N/A

SQL Queries

The following SQL shows how to find the total number of successful CI builds finished in the given time range.

SELECT
  count(*)
FROM 
  cicd_pipelines
WHERE
  result = 'SUCCESS'
  and $__timeFilter(finished_date)
ORDER BY 1

If you want to measure the monthly trend of the successful build count in the screenshot below, please run the following SQL in Grafana.

WITH _builds as(
  SELECT
    DATE_ADD(date(finished_date), INTERVAL -DAYOFMONTH(date(finished_date))+1 DAY) as time,
    count(*) as build_count
  FROM 
    cicd_pipelines
  WHERE
    result = "SUCCESS"
    and $__timeFilter(finished_date)
    -- the following condition will remove the month with incomplete data
    and finished_date >= DATE_ADD(DATE_ADD($__timeFrom(), INTERVAL -DAY($__timeFrom())+1 DAY), INTERVAL +1 MONTH)
  GROUP BY 1
)

SELECT 
  date_format(time,'%M %Y') as month,
  build_count as "Build Count"
FROM _builds
ORDER BY time

How to improve?

1. From the project dimension, compare the number of builds and success rate by combining the project phase and the complexity of tasks.
2. From the time dimension, analyze the trend of the number of builds and success rate to see if it has improved over time.