Open topic with navigation

Analyzing Code Commit Frequency

Let us look at a simple scenario to understand how you can use the CI Build iCube to analyze if the development teams are checking in their code frequently.

John is a Development Manager who is managing multiple teams working on multiple projects.

As a Development Manager, he wants to analyze how frequently are jobs being executed. In a continuous integration environment, the development teams are expected to submit their code changes frequently, as every check in triggers a job run. Analyzing the frequency helps him to identify outliers and reason out:

• If and why are there lapses in periodic code check-in
• If and which of the developers are not checking in their code periodically
• Other problem areas in job execution

Generating report

To analyze the frequency of jobs being executed, John must login to Digital.ai Intelligence Applications and perform the following tasks in the CI Build page:

1. From the GALLERY panel, select the desired visualization type .
   In this example, Bar Chart has been used.

From the DATASETS panel,

1. Drag and drop the Actual Build Duration (Secs) metric into the Metrics field of the EDITOR.
2. Drag the Estimated Build Duration (Secs) metric into the Rows field.
3. Drag the Job Name attribute into the Columns field.

Here is an example time duration analysis displayed as a bar chart:

Analyzing the report

Using the report, John can:

• Analyze estimated and actual build duration for jobs
• Reason out jobs that overshot the estimated duration