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.
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 fixA Buildkite organization with at least one pipeline.
The Buildkite GitHub App installed on your GitHub organization.
The Nullify GitHub App must have Commit statuses: Read permission and the Status event subscription enabled (see Configuration).
A Buildkite API token with read_builds and read_build_logs scopes.
GitHub already connected to Nullify.
Follow the Configuration guide to connect your Buildkite organization.
Last updated