The train that left every other Thursday
For six years a change waited up to two weeks for its seat. Missing the train meant waiting for the next one.
The carrier sorts parcels in nine depots, and each depot ran its own copy of the software. A release meant a night shift, a checklist of 140 lines and a room of people watching one screen.
One pipeline for nine depots
The team moved one service a week. Each got a preview address per branch and a build that reused what had not changed. The file release-checklist.md shrank until it was deleted.
We stopped planning releases. Now we only plan what to build.
What they changed, in order
- Previews for every branch, so that depot managers could try a change.
- Rollback as a button, tested weekly on a real service.
- The night shift for releases, ended in the fourth month.
A year later the median change reaches all nine depots 52 minutes after it is merged. The other logistics stories show the same curve.