Data and AI releases

811 this month · 176 companies

Choose read-only access when connecting Buildkite MCP

UpdateNot yet verified

Users can now select between Read-only and Full access when connecting an AI agent to Buildkite via MCP. Read-only access allows agents to inspect builds and logs without the ability to trigger changes.

MCPAI agents

Read on buildkite.com

Also shipped Nov 10, 2026Buildkite in November 2026 →

More from BuildkiteEvery Buildkite release →

Cancel in-progress jobs with concurrency groups

For finer control over concurrency group queues, cancel_in_progress: true lets a job waiting for a concurrency slot cancel blocking jobs in the same group: steps: command: "./real-device-tests.sh" concurrency: limit: 1 group: "my-pipeline/real-device-tests/${BUILDKITE_BRANCH}" cancel_in_progress: true The new concurrency map syntax keeps your limit, group...

Update
Source ↗

Trace propagation across triggered builds

Agent spans across your multi-pipeline workflows can now share a single OpenTelemetry trace without contacting Support to enable propagation. Buildkite automatically passes trace context from a parent build to builds it triggers. This also works for internal trigger chains without externally supplied trace context.

Update
Source ↗