Close a release with smoke and rollback evidence
Building an image does not prove that users can use a healthy path. Bind the tested commit to the running image and run a real DB-reading smoke after readiness.
0 viewsAbout 1 min read
Close a release with smoke and rollback evidence
Building an image does not prove that users can use a healthy path. Bind the tested commit to the running image and run a real DB-reading smoke after readiness.
Minimal sequence
- Require a clean worktree and explicit services.
- Build or reuse the Git-SHA image.
- Replace only target services with
--no-deps --force-recreate. - Check container readiness and each service's real read smoke.
- On failure, restore the previous image as a rollback tag and re-check readiness.
SSR and the static mirror
Docker SSR and a static mirror are separate artifacts. A DB-only change can leave the mirror with an old export, so verify console seed, SSR public reads, export contents, static deployment, and both locale routes separately. Preserve success and rollback logs with the release tag.
Related course: Bind a verified commit to a release and image