Promote the built artifact instead of rebuilding it
Staging and production-like environments run images compiled at different times from the same source label.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Artifact promotion · Immutability
Estimated field mix
- DevOps70%
- Cloud infrastructure30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional scheduling API is rebuilt separately for test, staging, and production-like local environments. The resulting images differ, release notes list the branch instead of the artifact, and rollback rebuilds old source with new dependencies. Use a local registry simulator and synthetic deployments; no cluster or customer traffic is supplied.
Setup prerequisites
- Artifact digests
- Release states
- Health checks
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Build creates one content-addressed artifact
- Promotion changes environment references without changing bytes
- Environment record retains promotion actor, time, and source environment
Implementation constraints
- Configuration remains external and versioned; it is not baked differently into each image.
Verification to include
- Promote one digest through two fixture environments and compare bytes.
- Attempt promotion with a mismatching manifest and block the transition.
Deliverables
- Promotion command and byte-identity tests
Rollout and recovery
Adopt from test to staging before changing the final environment.
Value of the work
For the engineer: Practice immutable promotion, release authority, compatibility gates, canaries, and rollback.
For the team: Review a delivery flow that can identify exactly what is running and restore a known artifact without rebuilding it.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.