buildkite.com/docs

Choose and implement a currently documented approach for handling secrets in Buildkite pipelines — Buildkite secrets, buildkite-agent secret get, environment hooks, or an external secrets manager plugin — while keeping values out of pipeline YAML and build logs.

Use buildkite-agent meta-data (set, set-batch, get, exists, keys) to pass small string key-value data between steps and jobs within the same build.

Use buildkite-agent annotate to attach Markdown-formatted status information to a build or job in the Buildkite UI, with configurable style, context, and append/update behavior.

Configure an outgoing Buildkite Pipelines webhook notification and verify that incoming deliveries are authentic using the X-Buildkite-Token or X-Buildkite-Signature HMAC header.

Create and manage cron-style scheduled builds on a Buildkite pipeline, both from the pipeline Settings UI and via the Pipeline Schedules REST API, including supported interval/cron syntax.

Get started making authenticated queries against Buildkite's GraphQL API: the endpoint, token permission, the interactive explorer, and how to address organizations/pipelines by slug or global ID.

List the artifacts attached to a build or a specific job, then download an artifact's contents via the REST API's redirect-based download endpoint.

Create a Buildkite pipeline (YAML or legacy visual-step), update its settings/configuration, and archive/unarchive or permanently delete it using the Pipelines REST API.

Retry a failed job, cancel a running build, or unblock a blocked ('Block pipeline') job in Buildkite via the REST API, including required scopes and the state each action requires.

Retrieve a Buildkite job's log output via the REST API, choosing between JSON, plain text, or HTML response formats, and know the caveats around size, ranges, and deleting logs.

List and filter Buildkite builds via the REST API, either across all accessible builds, org-wide, or scoped to a single pipeline, and correctly page through paginated results.

Authenticate to the Buildkite REST API using a personal API access token, understand the base URL and slug-based path structure, and know the current per-organization and per-user rate limits.

Add Buildkite agent lifecycle hooks to run custom logic at checkout and command stages of a job

Create a Buildkite build via the Buildkite REST API