12 releases · 1 product · 1 Preview
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.
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.
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.
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 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.
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.
The Buildkite VS Code extension is now available, bringing your pipelines and agents directly into your editor. You can browse and manage pipelines, view agent status, stream job logs, get build notifications, and validate pipeline YAML , all without leaving VS Code. Install it from the VS Code Marketplace .
A few things have shipped in the Buildkite MCP Server since list_tests arrived in August. Read the steps a dynamic pipeline uploaded You can now ask your agent what actually ran in a dynamic pipeline. list_step_uploads returns a build's uploads, most recent first, with the state of each one, the job that sent it, and the reason for any rejection.
Job logs are now limited to 1 GiB (1,024 MiB) by default. You can check your organization’s current log size limit on the Quotas page . When a job log exceeds the limit, Buildkite cancels the job and adds a Log Size Limit Exceeded event to the timeline. Logs received prior to the limit being reached are retained.
To improve GitHub Actions migration support , the Buildkite GitHub App now requests read-only access to Actions , Variables , and Environments . These permissions let Buildkite inspect configuration that affects how workflows and deployments run, including configuration variables referenced through ${{ vars.* }} , secret names (not secret values)...
Buildkite Agent v4 is here. It's the first major version of the agent since v3 arrived in 2018, and it's now the stable release: installations and upgrades that follow the latest or stable channels now receive v4.
Releasesby Glyph