## Buildkite integration details

**Category**: CI systems  
**Analyzed signals**: builds, build logs, CI failure analysis  
**Supported products**: Buildkite  
**Delivery**: CI Failure Agent reports in pull requests and merge requests  
**Content reviewed**: July 20, 2026

## What the Buildkite integration adds

Buildkite supplies detailed build output while Unblocked supplies the surrounding code and pull-request history. The CI Failure Agent combines those inputs to turn a failed build into a concise, confidence-gated explanation at the point where the change is being reviewed.

Because Unblocked already understands your codebase, pull requests, and team discussions, its analysis is grounded in that context — it explains what broke and suggests a fix, with links back to the relevant code and history.

Buildkite connects with a read-only API token plus a build-finished webhook, so Unblocked is notified the moment a build fails. Reports post as a comment on the pull request and are gated by confidence.

### What you get

- **Build-log failure analysis** — The CI Failure Agent reads your Buildkite build logs and analyzes failures across pipelines to find the root cause.  
- **Root-cause reports on the PR** — When confident, Unblocked posts a comment on the pull request explaining the failure and suggesting a fix.  
- **Grounded in your codebase** — Analysis draws on your indexed code, pull requests, and discussions, so suggestions fit how your project actually works.  
- **Confidence-gated, per-developer control** — Reports post only when Unblocked is highly confident, and each developer can toggle them for their own PRs in Personal Settings → Preferences.

## How to connect Buildkite to Unblocked

**Need screenshots or troubleshooting?** This is a concise connection summary. [Follow the complete setup guide](https://docs.getunblocked.com/data-sources/buildkite)

### Prerequisites

- An Unblocked account (free to start).  
- Your source code connected to Unblocked — the CI Failure Agent runs on your connected repositories.  
- A Buildkite API Access Token with read scopes, with Unblocked’s IP ranges allowlisted, plus permission to add a webhook notification.

### Connect Buildkite to Unblocked

1. In Unblocked, open Settings → Continuous Integration, click Add CI Provider, and click the Buildkite tile.  
2. Create a Buildkite API Access Token with the `read_build_logs`, `read_builds`, `read_organizations`, `read_pipelines`, and `read_user` scopes, and add Unblocked’s CIDR ranges to Allowed IP Addresses.  
3. Add a Buildkite webhook (Notification Services): paste Unblocked’s Webhook URL and Token, select the build-finished event, and enable all pipelines.  
4. Toggle the repositories you want to enable, then click Save Settings.

## Buildkite failures the agent can analyze

Examples of Buildkite failures the CI Failure Agent can investigate:

- Why did the Buildkite build fail on this pull request?  
- What is the root cause of the failing step in the pipeline?  
- Which recent change most likely caused the build failure?

## Related integrations

- [**GitHub Actions**](/content/integrations/github-actions/index.html) — Unblocked’s CI Failure Agent analyzes failed GitHub Actions runs on your selected repositories and posts root-cause reports to the pull request.  
- [**CircleCI**](/content/integrations/circleci/index.html) — The CI Failure Agent watches your selected CircleCI projects via webhook, analyzes failed builds, and posts root-cause reports to the pull request.  
- [**Jenkins**](/content/integrations/jenkins/index.html) — The CI Failure Agent analyzes failed Jenkins builds on your connected repositories and posts root-cause reports to the pull request.  
- [**GitLab Pipelines**](/content/integrations/gitlab-pipelines/index.html) — The CI Failure Agent analyzes failed GitLab pipeline runs on your selected projects and posts root-cause reports to the merge request.