How CI/CD works: why releasing code every day is safer than once a month
Continuous deployment: what changes when nobody presses the button
Some software teams have no deploy button at all: a change a developer merges after breakfast can reach every user before lunch. What continuous deployment changes, and what the "CD" in CI/CD really stands for.
-
1
The team tries Rono's idea and takes the button away. Now every change that passes every stage of the pipeline goes to production by itself.
-
2
You merge a small fix at 10:02, and by 10:25, the neighbours have it. No person looked at it on the way from main to their phones.
The rest of this episode is for subscribers
Subscribe to read every premium episode. You can cancel when you want.
Paid yearly: $99 instead of $119.88