Shipping / 2 / 2
CI/CD: from commit to production
A team deploys once a week, by hand, and every third deploy breaks something. Step by step the path from commit to production becomes automatic, small and reversible, and the team ends up deploying a dozen times a day.
- 14 min
- Intermediate
- 10 steps
- Deploys
- 0.1 /day
- Failed deploys
- 30 %
- Time to restore
- 5 400 s
- Error rate
- 40 %
- request
- reply
- redelivery
- duplicate
- lost
Numbers are a model scenario, not measurements
The real request
Developer → Blue serversRequest
$ ssh deploy@192.0.2.12
$ scp api-build.zip /srv/api/1
$ unzip -o /srv/api/api-build.zip
$ systemctl restart api2
api: missing env PAYMENTS_URL, exiting3
(same by hand on 5 more servers)
scp— A file copied by hand. Nobody can say later which build is on which server.restart— All users of this server are cut off during the restart.missing env— The new code needs a setting that exists only on the developer's laptop.
Course: 42 lessons
01 Foundations
02 Scaling
03 Data & storage
04 Communication
05 Reliability
06 Architecture
07 Security
08 Shipping
09 Whole systems
10 Business processes