During a suspected security incident, organization administrators can now revoke their organization's SSO sessions without contacting Support. Under Settings → Security, select Require SSO sign-in again to review and confirm the action. This revokes your organization's SSO sessions, including your own. Members who require SSO must sign in through your identity provider again before accessing the o…
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. HTTP traceparent header acceptance and Buildkite control-plane trace joining remain…
We’ve added a changelog menu to Buildkite. This changelog post is to let you know about the changelog menu, and is available in the changelog menu for that purpose. If you arrived at this changelog post through the changelog menu, you already know about the changelog menu. Please interpret this changelog post as confirmation that what you thought was the changelog menu was, in fact, the changelog…
You can now check out private GitHub repositories on self-hosted agents without distributing and rotating SSH keys or personal access tokens across your fleet. Buildkite supplies temporary, read-only GitHub App tokens for checkout, so a new machine, container, or Kubernetes pod doesn't need its own repository credential. The option is available to all customers and is off by default. In your self-…
Queue pages now give platform and CI teams a clearer view of how agents and jobs are moving through each queue. When work backs up or your agent fleet behaves unexpectedly, you can see where capacity is going and what is holding jobs back. Understand agent capacity: See how many agents are in use, idle, paused, or draining. See where jobs are: Distinguish jobs that are In progress, Starting up, Sc…
You can now manage Test Engine workflows with Terraform and the REST API instead of configuring each one in the UI. The new buildkite_test_suite_workflow resource in Buildkite Terraform provider v1.43.0 lets you define monitors, filters, and actions in code, and import existing workflows. For example, add a flaky label when a test becomes flaky and remove it when it recovers. The REST API lets you…
Buildkite Cache is now generally available on hosted and self-hosted agents. It gives every job a way to reuse work an earlier job already did, from a dependency download to an entire build command. It's built into the Buildkite agent as buildkite-agent cache commands you can call anywhere in a pipeline. Save and restore anything Define a cache in .buildkite/cache.yml, or any file you pass with --…
Webhooks can now send job events for only the queues you choose. If your autoscaler, dashboard, or alerting only cares about one queue, it no longer has to receive every job event in your organization and throw most of them away. For example, a GPU autoscaler can now receive job.scheduled events only for jobs on your gpu queue. When you add or edit a webhook in Notification Services, choose queues…
You can now turn on OpenTelemetry tracing for every agent in a cluster with one setting. Choose an OpenTelemetry notification service in the cluster's settings. Each agent that registers in the cluster then exports traces to that service's endpoint, using its headers, with no OTLP configuration on the agent. Until now, each agent needed its own OTLP endpoint, headers, and tracing flag. On hosted a…
Matrix steps previously appeared as a single node on the build canvas, with individual jobs shown in a separate panel. Now you can expand them in place to see each job's status and duration, and navigate directly to the job. Similar to group steps, failed matrix steps now start expanded and focus on failed jobs. Click show all to reveal the remaining combinations. Open a build that uses a matrix s…
Your test suite's Summary page now brings together more of the data you need to keep your suite healthy and fast, so you can see where time is going and where reliability is slipping without digging through individual tests. To find what's slowing your suite down, Slowest tests lists the 10 slowest tests in the selected period, and the suite and test duration distributions show how execution time…
You can now see when bk preflight or bk build watch finishes or needs you, without switching back to its tab. From Buildkite CLI v3.64.0, bk tells your terminal what it's doing, so a terminal that supports it can show you while you work somewhere else. bk reports its status using OSC 7501, a draft protocol that lets programs tell the terminal whether they're working, waiting on the user, done, or…
If your organization is on a monthly Pro plan, you can now see what your next invoice is shaping up to be before the billing period ends. Set a spend alert to get an email when the estimate reaches an amount you choose, so a busy month of builds doesn't become a surprise invoice. The new Usage & spend tab in Settings > Billing shows your estimated spend and the days left in the billing period, fol…
Your AI agent can now check the pipeline YAML it writes before you commit or upload it. The Buildkite MCP Server includes validate_pipeline, a read-only tool that checks YAML syntax and structure against Buildkite's pipeline schema, without uploading the pipeline or starting a build. Validation errors include paths and messages, giving your agent the information it needs to correct invalid step de…
Failed groups on the build canvas now put more focus on child steps that need your attention. When a group is failing or has finished with failures, expanding it shows only its failed steps. Click show all to reveal the hidden steps. Collapse and reopen the group to focus on failures again. State filters, such as Passed, still reveal matching steps.
Retry automation no longer needs the broader write_builds REST API scope. The new retry_builds scope allows a token to retry failed jobs in existing builds or individual eligible jobs, without granting access to the create-build or rebuild endpoints. When creating or editing an API access token, select Build Retries (retry_builds). Your existing user and pipeline permissions still apply, and token…
Buildkite shipped 40 releases. Three themes. Diagnosis. Agents put blocking failures first and retry infrastructure failures. Desktop alerts and log summaries are more reliable. Compatibility. GitHub Actions workflows get hashFiles() in composite actions, Windows checkout fixes, and retries for temporary token failures. Control. Track billable usage, manage memberships in Terraform, and choose wha…
Your agent can now do more of the work between a failed build and a green one. Here are the latest tool updates for the Buildkite MCP Server. See what changed since the last green build When a build fails, one of the first questions is what's different from the last one that passed. compare_builds answers it in a single call. It compares a build with the most recent earlier passing build on the sa…
You can now monitor your organization's billable active-user usage programmatically and compare it with your contracted allowance. Send the count to observability tools such as Datadog to track usage over time, or include it in internal license, billing, and compliance reporting. The Average monthly active users figure shown on the Organization Usage page is available through both Buildkite APIs:…
What shipped this week Between September 27 and October 3, 2026, we published 4 changelog entries and 35 releases across 13 public repos. Three things run through them: more control and predictability for platform teams, fewer gaps for teams moving off GitHub Actions, and more of the platform agents can drive directly. Tightened how secrets are handled. Pipeline-scoped secrets live in pipeline set…
You can now subscribe to RSS feeds for macOS base image releases on Buildkite hosted agents, making it easier to keep up with changes to your build environments. For updates to stable base images used in production, add the stable RSS feed to your preferred RSS reader. If your organisation wants access to the latest Xcode betas and runtimes, request a move to the canary channel. You can follow tho…
If you belong to more than one Buildkite organization, you can now choose which one each Remote MCP Server connection uses. Add the organization's slug to the server URL: https://mcp.buildkite.com/mcp?organization=your-organization When your MCP client asks you to authorize, that organization is already selected. This also works with toolset and read-only URLs, such as https://mcp.buildkite.com/mc…
From 1 January 2027, each minor release line of the Buildkite agent will be supported for one year from its first stable release. The final three months are a deprecation period: agents remain supported, with warnings encouraging you to upgrade. Installing an agent or updating to a newer patch doesn't restart that window. The policy applies to existing releases, using their original release dates:…
If you can edit a pipeline and manage its associated cluster, you can now create and manage secrets directly from Pipeline settings → Secrets. Pipeline secrets are cluster secrets with access restricted to the current pipeline. You can add branch, queue, build source, or creator conditions to narrow access further, and secret values remain hidden after creation. The new view keeps pipeline-specifi…
Job logs on the new build page are easier to scan now that Buildkite folds de-emphasized system groups into compact rows by default. Command output and the groups you usually need remain visible, while setup and other supporting output take up less space. Select a folded row to reveal just that section in place. The job log toolbar also lets you Show system groups temporarily and hide them again,…
Buildkite Cache is now available in public preview. It saves and restores files and directories across pipeline jobs and builds. Use it for package manager download caches, compiled dependencies, and other regenerable data to avoid repeating work. Define what to cache in .buildkite/cache.yml, then use buildkite-agent cache restore and buildkite-agent cache save in your pipeline. Cache keys let you…
Run a pipeline schedule as configured, or customize a one-off build without changing the schedule. Helpful when you need to validate your schedules before turning them on. Two actions on the schedule page make the choice clear: Run now asks for confirmation, then creates a build using the schedule's saved message, commit, branch, and environment variables. The build has source schedule, just like…
The Buildkite Agent Stack for Kubernetes Helm chart now includes built-in support for Slack App integration. You can configure Slack notifications directly in your Helm values without needing a separate sidecar or custom webhook setup. The chart handles token management and channel routing so your pipelines can post build status updates to Slack out of the box.
Understand PR retry patterns in your existing observability tool, without joining webhook data. Buildkite's server-side OpenTelemetry traces include PR metadata, including for GitHub merge-queue builds, and job retry metadata to compare manual and automatic retries and follow attempts. See how often PRs need retries and which repositories have the most retry activity. Comparing those patterns over…
Elastic CI Stack for AWS v7 is now available, bringing Buildkite Agent v4 to both Linux and Windows instances. Agent v4 clears out functionality deprecated since v3 arrived in 2018 and makes supported behavior the default. New capabilities have continued shipping in v3, so for most setups the move changes nothing about how you use the agent. Elastic CI Stack v7 updates its configuration to match.…