LoginSign Up
← Back to all sparks
Bitbucket logo

Bitbucket

DEVOPSINFRA · APIS
Velocity0.0

Code management

atlassian.com/software/bitbucket ↗

Pipelines stops being CI/CD and starts becoming an automation runtime.

ci-cdmerge-queuesagentic-automationpipelines-apimonorepomigration
◆Current state
Nearly every shipped item in this window lands on Pipelines rather than the repository or code-review surface. In one stretch Bitbucket opened Merge Queues to public beta, launched Agentic Pipelines for non-CI chores, added an API that runs pipeline definitions without a commit, extended artifact sharing to child pipelines, and added always-run final steps. Around that, Bamboo gets a migration tool ahead of its 2029 end of life and self-hosted runners get a pricing model.
◆Where it's heading
The pattern is a CI product being widened into a general execution engine: pipelines that are generated at runtime rather than committed, agents doing the work around code rather than building it, and queues arbitrating merges in monorepos where continuous merging breaks green builds. The Bamboo migration tool points the same way — Pipelines is being positioned as the destination for Atlassian's own CI installed base, not just the cloud-native option.
◆Prediction
Merge Queues entered open beta in this window and Agentic Pipelines shipped as an explicit first step, so the near-term moves are general availability for the queue and a broader catalog of agent tasks. The runner pricing change signals the self-hosted tier is being made economically sustainable rather than deprecated.

◆Recent moves

  1. 3mo ago

    Inside Atlassian’s Merge Queues: How we ship faster with fewer incidents

    An internal case study rather than a release — Atlassian describing its own Merge Queues rollout across 70-plus large repositories. It functions as evidence for the open beta shipped days earlier, not as a change to the product.

    View source ↗
  2. 3mo ago

    Introducing on-demand Pipelines: run pipelines via API

    Pipeline definitions can now be generated programmatically and executed through the Pipelines API with no commit, pull request, or YAML file in the repository. It extends the runtime-generated direction the rest of this window is pushing, though it builds on the existing API surface rather than opening a new one.

    View source ↗
  3. 3mo ago

    Share artifacts between parent and child pipelines

    Artifacts can now pass between parent and child pipelines, removing a coordination gap that limited how much real work could be delegated downstream. Incremental, but it makes child pipelines usable for multi-stage builds rather than isolated side jobs.

    View source ↗
  4. 3mo ago

    Merge Queues for Bitbucket Cloud, now in open beta

    ⚡ SPARK

    Merge Queues reach open beta, targeting the failure mode this trajectory keeps circling: high-velocity repositories where pull requests race each other to merge and semantically green builds still break. It is the first capability in this window aimed at the merge surface rather than the build surface.

    View source ↗
  5. 3mo ago

    Introducing Agentic Pipelines: AI automation for chores devs don’t want to do

    ⚡ SPARK

    Agentic Pipelines applies automation to the manual work that surrounds code rather than the build itself, and Atlassian frames it explicitly as a first step toward an agentic automation platform. That framing, more than the initial feature set, is what changes the product's stated direction.

    View source ↗
  6. 4mo ago

    Introducing: Final Steps in Bitbucket Pipelines

    Final steps run even when an earlier step fails, closing the familiar hole where a pipeline dies halfway and the cleanup never executes. A small addition, but one that makes runtime-generated and agent-driven pipelines safer to leave unattended.

    View source ↗