Skip to content

SYSTEM Cited by 2 sources

Bitbucket Pipelines

Atlassian's hosted CI/CD product, integrated directly with Bitbucket. On the sysdesign-wiki, the relevant surface is its role as an automated quality gate that the Rovo Dev agent reads output from and iterates against.

(Source: sources/2026-04-24-atlassian-rovo-dev-driven-development)

Role in the agentic workflow

Per the source post, the Fireworks team runs this CI surface on every PR:

"CI pipeline as quality gate: Every PR runs lint, vet, tests, and Helm validation. The agent reads pipeline output and addresses failures before requesting review."

Canonicalised as patterns/ci-as-agent-quality-gate. Key properties that make Bitbucket Pipelines fit this role:

  • First-class agent read access. The Rovo Dev agent has first-party access to pipeline output "without leaving the conversation" — the agent doesn't have to scrape a UI or invoke a CLI; the output is available as agent context.
  • Scope: lint + vet + tests + Helm validation. Covers the correctness surface end-to-end: static analysis (lint, vet), the test suite, and deployment-config validation (Helm).
  • PR-scoped. Every PR gets validated — the automated gate is always between the agent's output and the human review surface.

Seen in

Role in Merge Queues (2026-04-29)

Bitbucket Pipelines is also the execution substrate underneath Bitbucket Merge Queues. Two load-bearing configuration surfaces:

  • merge-queues: section in bitbucket-pipelines.yml — lets teams run a different, faster validation suite pre-merge without changing the post-merge pipeline that builds release artefacts. The merge-queue pipeline and the post-merge pipeline are deliberately distinct; bundling them would turn queue latency into a ceiling on release-pipeline cost.
  • Parent-child pipelines for merge-queue parallelism — Jira's merge-queue pipeline fans out to three parallel parent-child pipelines (one per product distribution). Pattern canonicalised as patterns/parent-child-pipelines-for-ci-parallelism.

On the agent-side, Bitbucket Pipelines also functions as the CI surface Rovo Dev reads output from and addresses before requesting review (see patterns/ci-as-agent-quality-gate). Together these two roles make Pipelines a dual quality gate: a defensive checkpoint for human-authored merges via the merge queue, and a feedback channel for agent-authored PRs via direct agent integration.

Last updated · 542 distilled / 1,571 read