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
- Log into your TierZero dashboard
- Go to Settings → Integrations
- Click Connect next to Buildkite
Step 2: Create an API Token
- In Buildkite, go to Personal Settings → API Access Tokens
- Click New API Access Token
- Name it (e.g., “TierZero Integration”)
- Select your organization
- Grant Read access to the required scopes (builds, pipelines, agents)
- Click Create
- Copy the token
Step 3: Enter Credentials
- Paste the API token into TierZero’s setup field
- Enter your Buildkite organization slug
- 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, configure Integration Resources to help TierZero 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, 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