CI and Release Integration¶

Scope¶

bf-dev includes pipeline definitions and release-note tooling used to coordinate downstream repositories.

Key Assets¶

• .gitlab-ci.yml
• ci-templates/
• subtrees.txt

Pipeline Concept¶

flowchart LR
  Source[Repo changes] --> CI[bf-dev root pipeline]
  CI --> Inputs["Run pipeline inputs"]
  CI --> Release["Release note workflows"]
  CI --> Subtree[Manual subtree sync job]
  Inputs --> Downstream[Downstream release-branch orchestration]

Notes¶

• Subtree sync is controlled by subtrees.txt entries.
• Release note helpers live in bf-release scripts.
• The root .gitlab-ci.yml is the operator-facing orchestration entrypoint for release-branch and notes publishing workflows.
• The action input asks what do you need to do? and currently exposes:
• bring-all-code-to-release-branch for the cut-off path
• deploy-release-branch-to-staging for the release-branch staging path
• The project input asks what project/s need it? and accepts one supported repository or all.
• The confirm input must be set to true before UI-driven orchestration starts.
• INVOKE_CUT_OFF and INVOKE_RELEASE remain as compatibility paths for the all fan-out workflow.
• The root pipeline and retained release-note include also provide the MR dry-run trigger used by downstream Terraform-plan workflows. The operator runbook lives in Terraform Plan Dry Runs.
• The operating model for release-note structure and weekly promotion lives in docs/process/guides/release-notes.md.
• This repo orchestrates integration and process, not downstream service releases directly.