> For the complete documentation index, see [llms.txt](https://docs.logilica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.logilica.com/metrics-and-reports/build.md).

# Build

## Purpose

Team productivity can be severely impacted by the infrastructure they rely on. This includes build times, reliability, and recovery times. This report provides insights into critical build metrics across pipelines and teams to pinpoint areas of improvement.

{% hint style="success" %}
**Improvement Actions**: Once overall build performance is tracked, it is helpful to tackle those build pipelines that have:

* low reliability,
* a high number of developers depend on them, and
* each individual build might take a long time.

A combination of the above might block contributors in their productivity and also hamper fast, reliable releases. Improving infrastructure speed and reliability leads to higher levels of team happiness and productivity.
{% endhint %}

## Supported CI/CD Platforms

Build data is imported from the following platforms:

| Platform             | How It Connects                                          |
| -------------------- | -------------------------------------------------------- |
| **GitHub Actions**   | Enabled via the GitHub or GitHub Apps connector settings |
| **GitLab Pipelines** | Enabled via the GitLab connector settings                |
| **CircleCI**         | Standalone connector with API Token                      |
| **BuildKite**        | Standalone connector with API Token                      |

You can also push build data from any CI/CD system via the [Import API](/advanced/import/build-data.md).

## Build Hierarchy

Logilica models CI/CD data in a three-level hierarchy:

* **Pipeline** — the top-level build (e.g., a GitHub Actions workflow run or a GitLab pipeline)
* **Stage** — a grouping of jobs within the pipeline (e.g., a GitHub Actions job or a GitLab stage)
* **Job** — individual steps within a stage

You can drill down from pipeline to stage to job to identify exactly where failures or slowdowns occur.

## Explanations

The build report provides a number of insights, including:

**Total number of builds**: This helps to observe the overall build frequency trend.

**Reliability**: The overall reliability of corresponding pipelines of all selected teams and repositories. Low reliability is known to reduce productivity significantly.

**Build speed**: The time it takes on average for a build. Builds are potential blockers for teams to get their work done, and long build times might slow teams down significantly.

**Recovery time**: The average time it takes for a broken build to recover. Long recovery times potentially block teams for a similar time and might stall releases.

**Build result breakdown**: The success rate and breakdown of builds over time. It shows the trend of improvements or degradation and sometimes the causes for unsuccessful builds.

**Build pipeline table**: The table breaks down each build pipeline into criteria similar to the above. This is a good starting point to identify bottlenecks and unreliable builds.

## DORA Metrics Connection

Build data is the foundation for [DORA metrics](/configuration/dora-configuration.md). When you configure [Release Detection](/configuration/release-detection.md), Logilica flags specific builds as deployments and calculates:

* **Deployment Frequency** — how often deployments happen
* **Lead Time for Changes** — time from PR merge to deployment
* **Change Failure Rate** — percentage of deployments that fail
* **Mean Time to Recovery** — how quickly failed builds recover

See [DORA Configuration](/configuration/dora-configuration.md) for setup details and performance tier benchmarks.

## Good to Know

You can drill down into each pipeline individually to examine the history of the build, its success rate and the stages at which the build has failed.

By default, Logilica imports a history of the last 1000 build runs per repository at the initial onboarding time. Future build runs will be added to the stored history.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.logilica.com/metrics-and-reports/build.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.