LoginSign Up
← Back to all sparks
B

Buildkite

INFRA · APIS
Velocity5.0

Buildkite makes caching a built-in agent primitive and puts test workflows into Terraform.

ci/cdbuild cachingtest engineinfrastructure as codeobservability
◆Current state
Buildkite is a CI/CD platform that combines a hybrid agent model with a growing Test Engine. Its October releases include built-in caching (now GA), Terraform and REST management of Test Engine workflows, queue-filtered webhooks and cluster-level OpenTelemetry. The product is filling infrastructure gaps that teams previously solved with plugins or custom images.
◆Where it's heading
The pattern is to centralize and codify: settings move from individual agents to clusters, and from the UI to Terraform and APIs, and capabilities such as caching move from plugins into the agent itself. Test Engine is turning into a programmable flaky-test management layer instead of a dashboard.
◆Prediction
Expect more Test Engine monitors and actions that can be managed in code, and cache controls such as eviction and scoping, now that Cache is GA.

◆Recent moves

  1. 1d ago

    See what's happening across your agents and queues

    Queue pages now break agents down by state and jobs by why they are waiting, with an activity chart on a more reliable data source and up to 25 sample jobs per state. It continues October's platform-team work on queues, after queue-filtered webhooks and cluster-level OpenTelemetry.

  2. 6d ago

    Manage Test Engine workflows with Terraform and the REST API

    Test Engine workflows, including monitors, filters and actions such as flaky labeling, can now be defined in Terraform provider v1.43.0 or managed through the REST API. It brings test policy into the same infrastructure-as-code flow Buildkite users already use for pipelines.

  3. 7d ago

    Buildkite Cache is generally available

    Buildkite Cache is GA on hosted and self-hosted agents, with buildkite-agent cache save and restore commands, key-based configuration and fallback to recent entries. It replaces the plugin and DIY approaches teams used for warm builds, matching what competing CI platforms already offer natively.

  4. 8d ago

    Filter webhook job events by queue

    Webhooks can send job events only for selected queues, so a GPU autoscaler no longer has to filter the whole organization's event stream. It's a practical scaling fix for teams running custom autoscalers.

  5. 9d ago

    Configure OpenTelemetry at the cluster level

    Cluster-level OpenTelemetry removes the per-agent OTLP setup that forced hosted users to build custom images, and existing agent overrides keep working. It moves another operational chore into the control plane, though jobs can read the exporter token, so Buildkite advises a send-only token.

  6. 10d ago

    Inspect matrix jobs directly on the build canvas

    Matrix steps stop collapsing into a single canvas node: each job's status and duration is visible in place, and failed matrices open expanded on the failing combinations. It is the same failure-first treatment group steps got on October 13, extended to the step type where failures were hardest to find.