Build, test and deploy
Every change is tested and built the same way, shipped in one step, checked for health, and rolled back by itself when something fails.
- Required 3
- Recommended 2
Required
Unit test the tricky parts
RequiredTest logic that can break silently on its own, without a network, a database or a browser.
Deploy in one step and roll back by itself
RequiredUpload next to the live copy, swap in one step, health-check, and put the old copy back if the check fails.
Give the server a health check
RequiredGive the server a health check address that tests its dependencies, so deploys and monitors know when it is broken.
Recommended
Run the tests inside the container build
RecommendedMake it impossible to produce a deployable image from untested code.
Release to a small share first
RecommendedSend a new release to a small share of traffic first, compare it with the old one, and roll back by itself when errors rise.
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers engineering playbook: https://agentwranglers.se/playbook/engineering/build-test-and-deploy.