SYSTEM Cited by 1 source
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¶
- sources/2026-04-24-atlassian-rovo-dev-driven-development — the CI surface Rovo Dev reads and iterates against during the Fireworks build.