How CI/CD works: why releasing code every day is safer than once a month
Pipeline stages: why a CI pipeline runs the fastest checks first
A CI pipeline that takes forty minutes slowly gets ignored: people stop waiting for it, and then they push less often. Why the order of the checks matters so much, and which tests run while everybody sleeps.
-
1
The pipeline has grown to forty minutes. It runs the slow tests first, the ones that tap through the whole app like a neighbour would, and the hundreds of small tests after them, in the order someone once wrote them.
-
2
On Monday, you push a small mistake that one small test catches. The cross comes after thirty-nine minutes, when you are deep in another task, and the team has started to push less often to wait less.
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