Skip to content

Bitbucket Workers CI/CD

Build and deploy Cloudflare Workers from Bitbucket, for the engineering teams that keep Bitbucket as their primary code repository.

  • Owner: Jeffrey Lambert
  • Status: Proposal under review. Option A (Bitbucket Pipelines) is the recommended path; ratify, then promote into the Workers SOP.
  • Started: 2026-07-16
  • Applies to: Any Adventive Worker whose source lives in Bitbucket rather than GitHub or GitLab.
  • Promotion target: On ratification, this content is promoted and cross-linked into system-infrastructure/cloudflare/workers/ alongside the QA and Deployment SOP.

Cloudflare’s native CI/CD, Workers Builds, integrates only with GitHub and GitLab. Teams that develop Workers in Bitbucket cannot use it. This project documents how those teams build and deploy Workers on the same gate sequence, environments, and secrets model the rest of the platform already uses.

  • Context: the constraint, the teams affected, and what stays the same across providers.
  • Options: the three viable pipelines, with tradeoffs and a recommendation.
  • Implementation: the step-by-step Cloudflare and Bitbucket configuration for Option A, dev through production.
  • Design pillars: how the pipeline satisfies the six mandatory Cloudflare design pillars.
  • Appendix: references, glossary, and the full bitbucket-pipelines.yml.
  • Decisions: the ADR selecting Bitbucket Pipelines as the primary path.
  • Adventive_Bitbucket_Workers_CICD_Implementation.pdf: the comprehensive implementation guide, WeasyPrint house style. Regenerate with build_pdf.py.
  • QA and Deployment SOP: ../../system-infrastructure/cloudflare/workers/qa-deployment-process.md
  • Wrangler Configuration Standard: ../../system-infrastructure/cloudflare/workers/wrangler-configuration.md
  • Secrets and Security Policy: ../../system-infrastructure/cloudflare/workers/security-secrets-policy.md
  • Cloudflare CI/CD docs: https://developers.cloudflare.com/workers/ci-cd/