How CI/CD works: why releasing code every day is safer than once a month
A broken build: why a red main branch stops the whole team
One developer pushes a broken change to main just before six in the evening and goes home. The next morning, the whole team is stuck, though nobody else touched that code. Why a red build in the main branch is everyone's problem, and the fastest way out.
-
1
On Thursday at 17:55, Miva pushes a change to main and goes home. Eight minutes later, main turns red.
-
2
On Friday morning, Rono pushes his own change, and main is red again. He cannot tell whether the cross is his or still Miva's, and while main is red, nothing in it can go to the neighbours.
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