Data and AI releases

548 this month · 176 companies

Job logs are limited to 1 GiB

UpdateNot yet verified

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.

PricingObservabilityDeveloper tools

Read on buildkite.com

Also shipped Sep 3, 2026Buildkite in September 2026 →

Genie One enhancements

- Ask Genie button hidden when unsupported : In embedded dashboards, the Ask Genie button is now hidden when it isn't supported. See Ask Genie in embedded dashboards . Push notifications for scheduled tasks (Public Preview) : The Genie mobile app can now send push notifications for scheduled tasks to iOS devices. See Push notifications .

Preview
Source ↗

Web search in Genie One (Beta)

Genie One can now search the public web to answer questions that need current information, such as recent releases, third-party documentation, or news. Genie One decides when to search and cites the sources it uses, showing each as a link you can open. See Search the web .

Beta
Source ↗

More from BuildkiteEvery Buildkite release →

Read-only GitHub Actions, Variables, and Environments permissions

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)...

Update
Source ↗

Buildkite Agent v4 is here

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.

Update
Source ↗

Buildkite MCP Server updates

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.

Update
Source ↗

Buildkite for VS Code

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 .

Update
Source ↗

Understand pull request retry patterns with OpenTelemetry

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.

Update
Source ↗

Elastic CI Stack v7 is here with Buildkite Agent v4

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.

Update
Source ↗

Buildkite Helm chart: Slack App integration

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.

Update
Source ↗

Test your schedules with or without edits

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.

Update
Source ↗