> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tierzero.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Buildkite

> CI/CD platform for running build and deployment pipelines

## Overview

Connect your Buildkite organization to give TierZero access to your CI/CD pipelines, build results, and test suites. TierZero uses Buildkite to analyze build failures, detect flaky tests, and correlate deployments with incidents.

## Prerequisites

* Administrative access to your Buildkite organization
* Permission to create API tokens

## Setup Instructions

### Step 1: Navigate to Integration Settings

1. Log into your TierZero dashboard
2. Go to **Settings → Integrations**
3. Click **Connect** next to Buildkite

### Step 2: Create an API Token

1. In Buildkite, go to **Personal Settings → API Access Tokens**
2. Click **New API Access Token**
3. Name it (e.g., "TierZero Integration")
4. Select your organization
5. Grant **Read** access to the required scopes (builds, pipelines, agents)
6. Click **Create**
7. Copy the token

### Step 3: Enter Credentials

1. Paste the API token into TierZero's setup field
2. Enter your Buildkite organization slug
3. Click **Connect**

## What TierZero Accesses

* **Pipelines**: Pipeline configurations and metadata
* **Builds**: Build results, logs, and timing
* **Jobs**: Individual job results and artifacts
* **Test suites**: Test analytics and flaky test data
* **Annotations**: Build annotations for context

## Integration Resources

After connecting Buildkite, TierZero uses these resource catalogs to understand your pipelines:

* **pipelines.json**: Pipeline names, slugs, descriptions, and relevant annotations/artifacts
* **test\_suites.json**: Test suite configurations

## Capabilities

Buildkite pipelines can be used as [Capabilities](/features/capabilities), which are workflow automations that TierZero can trigger during investigations (e.g., rollback pipelines, diagnostic builds).

## Security

* TierZero uses a scoped API token with minimal permissions
* Tokens are encrypted at rest
* Revoke access by deleting the API token in Buildkite

## Troubleshooting

### Pipeline Not Visible

* Verify the API token has access to the correct organization
* Check that the token has the required read scopes