Rollback to a known artifact without rebuilding source
The rollback command checks out an old tag and rebuilds it with current dependencies, producing bytes never previously tested.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Rollback · Artifact retention · Incident response
Estimated field mix
- DevOps70%
- Site reliability30%
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
- Rollback selects a previously promoted immutable digest
- Compatibility gate evaluates current schema and configuration
- Release history records the failed and restored identities
Implementation constraints
- Rollback does not delete the failed artifact or rewrite its record.
Verification to include
- Roll forward, trigger the abort rule, and restore the exact prior digest.
- Remove the prior artifact from the registry fixture and block rollback with a recovery instruction.
Deliverables
- Digest-based rollback command and rehearsal
Rollout and recovery
Maintain at least one verified compatible rollback target per 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.