18 · CI, registry, rollback
Release pipeline
Build once, deploy by digest, roll back without a person.
Shared pipeline templates test and build an image once, deploy it by digest to a test line that rolls itself back on a failed check, and promote to production by a manual step with its own rollback.
- 01Shared templates — Go and Node services include one template that tests, builds rootless and pushes.
- 02Deploy by digest — the deploy host takes only an exact digest, waits up to five minutes for ready, and restores the previous image otherwise; its key can run nothing else.
- 03Test line, then promote — a manual promotion to production, with a separate rollback job.
- 04One-click promote (on a branch) — gate, promote, check, roll back on failure and report, in one job; not yet on the main line.
- 05CalVer tags — the next vYY.M.PP for each image is planned from the registry.
Internal
- 12 estate pipeline jobs
- 3 shared templates
- 2 registry kinds
SurfacesCLISelf-hosted
- GitLab CI
- BuildKit (rootless)
- Container registry
- Podman
- Bash
- SSH forced command