1. Can the artefact be built from nothing?
If your service ships as a container image, build it from a fresh checkout with no cache, for the platform the server uses, and start a container. Everything later in this path assumes a build that does not depend on a warm laptop.
- Clean-checkout differences: the laptop-versus-CI guide.
- Processor mismatch: the wrong-architecture guide.
- Bounded fix: the image-build job from £245.
2. Can a reviewer see each change running?
A preview for every pull request needs test settings and a policy for fork pull requests. Without it, problems are found after merge.
- Safe preview settings: the preview guide.
- Bounded fix: automatic previews from £695.
3. Is each release numbered and described by the pipeline?
Versions should follow agreed rules and the notes should group changes. A tool needs full history and tags to compute them, and a failed release must be safe to retry.
- Version needs history: the release-history guide.
- Safe retry: the failed-publish guide.
- Bounded fix: versioned releases from £595.
4. Do you know what going back restores?
Name an earlier release, rehearse the return on staging and write down what a rollback does not undo: data, settings and work in flight.
- What cannot be undone: the rollback guide.
- Bounded fix: a rehearsed rollback from £595.
5. Will you know when it stops working?
Release machinery decays. A monthly rehearsal of the dry run, the clean build and the staging rollback shows drift before an emergency, at £395 a month. Doing parts two, three and four together as one pipeline is a project from £2,250 after a quote; the image build in part one is added at its own price.
- Monthly rehearsal: the standing service.
- All three parts in order: the project.
Sources and limits
- Docker multi-platform builds Checked 2026-10-11.
- An image must match the host's CPU architecture unless emulation is involved.
- Vercel Instant Rollback Checked 2026-10-11.
- A rollback reassigns domains to an earlier deployment and does not change environment variables.
- Semantic Versioning 2.0.0 Checked 2026-10-11.
- A released version's contents must not be modified; any change ships as a new version.