# Buildkite

## Overview

Use the Buildkite connector to give Nullify visibility into your CI/CD pipeline results. Once connected, Nullify can:

* Detect failing Buildkite builds on autofix pull requests.
* Fetch build logs from the Buildkite API to understand why CI failed.
* Automatically iterate on fixes using the failure output as context.

This enables the full autofix iteration loop for teams that use Buildkite as their CI runner alongside GitHub for source control.

## How It Works

When Nullify pushes an autofix commit to a pull request, Buildkite runs your CI pipeline. If the build fails, Buildkite reports the result back to GitHub as a commit status. Nullify detects this status event, fetches the build logs from the Buildkite API, and feeds the failure output to the autofix agent so it can iterate on the fix.

```
Autofix push → Buildkite CI runs → Build fails →
GitHub commit status → Nullify detects failure →
Fetches Buildkite logs → Agent iterates on fix
```

## Prerequisites

* A Buildkite organization with at least one pipeline.
* The [Buildkite GitHub App](https://buildkite.com/docs/integrations/github#connect-your-buildkite-account-to-github) installed on your GitHub organization.
* The Nullify GitHub App must have **Commit statuses: Read** permission and the **Status** event subscription enabled (see [Configuration](/connectors/buildkite/configuration.md#github-app-permissions)).
* A Buildkite API token with `read_builds` and `read_build_logs` scopes.
* GitHub already connected to Nullify.

## Next Steps

Follow the [Configuration](/connectors/buildkite/configuration.md) guide to connect your Buildkite organization.


---

# Agent Instructions: 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.nullify.ai/connectors/buildkite.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.