CI/CD & Promotion
How change moves from Dev to UAT to Production through a release pipeline, and never by hand.
Principle
UAT and Production are written into, never authored in.
Development is authored in Dev and committed out of it. Downstream environments are outputs of the release pipeline, so what is running upstream is always exactly what is in the branch.
Structure
Authoring
Integration
Release
Branch-to-environment mapping.
Procedure
- 01
Bind each workspace to a branch
One environment, one branch, no exceptions. Placeholder body copy to be completed.
- 02
Author only in Dev
Changes are made in the Dev workspace and committed to the feature branch. Placeholder body copy to be completed.
- 03
Promote through the pipeline
Deployment to UAT and Production is executed by the pipeline against a merged branch. Placeholder body copy to be completed.
- 04
Keep parameters outside the artefact
Environment-specific values are supplied at deployment time. Placeholder body copy to be completed.
Verification
- No direct edits exist in UAT or Production.
- Each environment maps to exactly one branch.
- A deployment can be reproduced from the branch alone.
- Rollback is a pipeline run, not a manual repair.