Versions Compared

Old Version 4

changes.mady.by.user Roopa P

Saved on

compared with

New Version 5

changes.mady.by.user Pragyan Sundarray

Saved on

Key

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

Overview

Definition (Hover Text)

Build frequency refers to the number of successful code builds done in a specific time frame.

Source Tools

Jenkins, Bamboo, Github Action, Azure Pipeline, Teamcity, Argo CD

Graph type

Line chart

Filters

Job FilterName ( as per tool configuration )

Hover Format on KPI

Date Range: <<Count of Successful Builds>>

Fields on Overlay

  • Project Name

  • Job Name

  • Weeks

  • Start Date

  • Build URL

Business Logic

Calculation Formula

-Count of successful code builds per week

Trend

Higher the count better is the ‘Speed’

Maturity Levels

M0: 0

M1: 1

M2: 2-4

M3: 5-8

M4: 8-10

M5: >10
Please note:- KPI widget denotes the average maturity over data points

Instance level thresholds

8 builds per week

Configurations

Processor Fields

N/A

KPI Specific fields

N/A

How to Validate KPI

Suggested ways of working

Sample JQLs

NA

Benefits of KPI

How does the KPI help

  1. Ensuring code changes are integrated regularly.

  2. Detecting integration issues early on.

  3. Promoting faster delivery and feedback.

...

Check the total no. of builds and deployments done weekly in your CI/CD pipeline

Best Practices

Automate Testing

Ensure that automated tests are run with each build to catch issues early and provide immediate feedback.

Use Version Control

Encourage developers to commit small, incremental changes frequently rather than large, infrequent updates.

Enforce Code Quality Standards

Implement code quality checks and enforce coding standards to reduce the likelihood of build failures.

Monitor Build Health

Use build monitoring tools to track the status of builds and quickly address any failures.

Benefits of KPI

Early Detection of Issues

Frequent builds help in identifying integration issues early, reducing the time and effort needed to resolve them.

Faster Feedback Loop

Regular builds provide faster feedback to developers, allowing them to address problems sooner and improve the quality of the software.

Improved Product Quality

By regularly building and testing the software, teams can maintain higher quality standards and ensure that the product is always in a deployable state.

Better Visibility

Continuous builds provide better visibility into the progress and health of the project, allowing stakeholders to track development more effectively.