CI/CD is an evidence pipeline
An enterprise CI/CD pipeline should answer two questions: is this exact source safe enough to package, and is this exact artifact safe enough to promote to the next environment? Rebuilding differently per environment or skipping gates turns deployment into a manual experiment.
Separate verification from promotion
- Run formatting/lint, types, unit tests, integration/contract tests, content/security checks, and build before publishing an artifact.
- Generate one immutable artifact with source revision and dependency provenance.
- Promotion should change environment configuration, not rebuild application code.
- Database migration compatibility and rollback/forward-recovery must be evaluated before traffic shift.
- Protect production deployment with environment permissions and auditable approvals where required.
Gates from commit to production
A commit passes deterministic gates, produces one signed/versioned artifact, then that artifact moves through staging and production with deployment-specific smoke checks.
Verification produces evidence; promotion reuses it
A commit passes deterministic gates, produces one signed/versioned artifact, then that artifact moves through staging and production with deployment-specific smoke checks.
1
CommitStart
2
Quality + testsStep
3
Security + buildStep
4
Publish artifactStep
5
Deploy stagingStep
6
Approval / promoteStep
7
Production smokeOutcome
Promoting a banking-channel release
Pipeline shortcuts that weaken assurance
Enterprise pipeline checklist
- Make clean install deterministic.
- Fail closed on lint/types/tests/security/build.
- Attach source revision and checksums to the artifact.
- Promote the same artifact through environments.
- Audit production approval, migration outcome, smoke checks, and rollback decision.