Bind preview updates to the exact requested source revision
A slow build for an older commit finishes after a newer build and replaces the current preview.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Concurrency · Deployment state
Estimated field mix
- Platform engineering60%
- Distributed systems40%
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 team creates preview stacks for pull requests. Orphan databases consume resources and previews sometimes inherit settings intended for another branch.
Setup prerequisites
- Create a local provisioning adapter with synthetic repository events.
- Use isolated disposable resources and no production credentials.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Track requested generation and source revision.
- Only the current generation may become active.
- Keep stale build artifacts visible for cleanup but never route traffic to them.
Implementation constraints
- Do not treat completion time as revision order.
Verification to include
- Complete two builds in reverse order and activate only the latest requested one.
- Retry stale activation and preserve the selected generation.
Deliverables
- Generation guard and completion-order tests
Rollout and recovery
Enable guarded routing; restore the prior valid generation if the new one fails readiness.
Value of the work
For the engineer: Practice resource lifecycle, reconciliation and least-privilege setup.
For the team: Review reliable preview workflows and accountable resource cleanup.
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.