> 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/integration/connecting-tools/buildkite.md).

# Buildkite

The Buildkite connector imports your builds into Logilica so build performance and reliability feed into the [Build dashboard](/metrics-and-reports/build.md), and — once deployment detection is configured — the [DORA metrics](/configuration/dora-configuration.md).

## Authentication

Buildkite is a standalone connector authenticated with a Buildkite API token. Logilica uses the token to discover the pipelines that match each connected repository within your Buildkite organisation, then imports the builds for those pipelines. The token needs the `read_builds`, `read_organizations`, `read_pipelines`, and `read_user` scopes, and you must select the organisation to import from. See [Connecting Tools](/integration/connecting-tools.md) for how to add the token and supply your organisation and repository details.

{% hint style="info" %}
**Your organisation slug and repository URL are required.** Logilica matches Buildkite pipelines to a repository using the organisation slug and the repository's remote URL. If either is missing, no build data is imported for that repository.
{% endhint %}

## What's Imported

For each matched pipeline, Logilica imports builds and the work beneath them:

* **Builds** — the pipeline name, a link to the build in Buildkite, and the build's created, started, and finished times
* **Build outcome** — whether the build succeeded, failed, or was cancelled
* **Triggering actor** — the person who triggered the build
* **Commit and branch** — the commit hash and branch
* **Jobs** — each job in the build, with its name, timestamps, and link

## How Logilica Maps the Data

Build outcomes are normalised so that success, failure, and cancelled results are consistent across every CI/CD platform Logilica supports.

{% hint style="info" %}
**Running builds are skipped.** Only builds that have finished are imported. In-progress builds are left out until they finish and are picked up on a later scan.
{% endhint %}

## Good to Know

* **Kept in sync automatically.** After the initial import, Logilica refreshes this connection on a regular schedule — you don't need to re-trigger imports.
* **First import covers the last 6 months.** The initial scan imports builds created within the last 6 months, paging back through history until it reaches that window. Importing older history requires a configuration change by Logilica — contact support.
* **Up to 1000 builds per pipeline.** Logilica imports up to roughly the most recent 1000 builds per pipeline at onboarding. Future builds are added to the stored history as they complete.
* **Build authors are attributed.** The people who trigger your builds are matched to their Logilica identities, so build activity is attributed correctly.
* **It feeds Build and DORA.** Imported builds power the [Build dashboard](/metrics-and-reports/build.md) (build frequency, reliability, speed, and recovery time) and, once [Release Detection](/configuration/release-detection.md) is configured, the [DORA metrics](/configuration/dora-configuration.md).
* **Push your own build data.** If you run builds that this connector doesn't cover, you can send them via the [Build Data Import API](/advanced/import/build-data.md).