← Back to all sparks
B

Buildkite

INFRA · APIS
Velocity5.0

Buildkite lets a new job cancel the ones blocking it in a concurrency group.

ci/cdpipeline-concurrencysecuritygithub-actions-parityself-hosted-agents
◆Current state
Buildkite's recent changelog fills gaps that used to need a Support ticket, a plugin or a workaround. Admins gained self-serve controls to force SSO sign-in and revoke all OAuth tokens, artifact retention became adjustable, and self-hosted agents can check out GitHub code with short-lived tokens. Concurrency groups now take cancel_in_progress, so a newer job can cancel older jobs holding the slot.
◆Where it's heading
The pattern is closing small, concrete gaps against GitHub Actions habits and enterprise checklists rather than shipping a headline feature. The concurrency change even names buildkite-gha compatibility, a sign Buildkite is courting Actions users who expect the same pipeline semantics.
◆Prediction
More Actions-parity features in pipeline syntax look likely, given that cancel_in_progress shipped alongside a buildkite-gha release that maps the same setting.

◆Recent moves

  1. 1d ago

    Cancel in-progress jobs with concurrency groups

    cancel_in_progress lets a waiting job cancel the jobs blocking its concurrency group, the behaviour GitHub Actions users expect for branch builds. A new concurrency map keeps limit, group and method together without breaking old configs, and buildkite-gha maps Actions' own setting to it.

  2. 5d ago

    More control and visibility for artifacts

    Admins can now shorten retention for Buildkite-hosted artifacts and see storage and download usage against plan inclusions over time. It continues the move to self-serve controls, here aimed at cost rather than security.

  3. 5d ago

    Revoke OAuth access for your organization

    Admins can revoke every OAuth access and refresh token for the organization in one action, including CLI and remote MCP connections, without contacting Support. Paired with the SSO revoke, it gives incident responders a self-serve containment kit; personal API and agent tokens still need separate handling.

  4. 6d ago

    Require SSO sign-in again for your organization

    Admins can force every SSO session in the organization to sign in again from Settings, a step that used to need Support. Tokens are deliberately left alone, so this works as the first half of an incident-response pair with the OAuth revoke.

  5. 8d ago

    Buildkite adds a changelog menu with an unread badge

    A new changelog menu in the Buildkite header, with a badge for unread posts. Navigation only.

  6. 8d ago

    Trace propagation across triggered builds

    Trace context now passes automatically from a parent build to the builds it triggers, without asking Support. It extends the October OpenTelemetry work from single pipelines to multi-pipeline workflows.