Case study
Making deploying boring — and in doing so, making it frequent.
Meridian shipped twice a week and dreaded both. Fifteen-minute builds, failures nobody could reproduce, and a rollback plan that was a person who knew which commit to revert.
Fig. 1 — the problem
The pipeline wasn't slow, it was repetitive. Three of the fifteen minutes were work; the rest was the same dependency tree resolved four times across four jobs that each started from nothing.
Fig. 2 — what we found
One cached install shared across jobs, type checking moved off the critical path, a preview URL per pull request, and rollback that promotes a previous build instead of reverting source.
Fig. 3 — the fix
“The build wasn’t waiting on the code. It was waiting on itself.”
4m 05s
median build, from 15m 20s
11
releases a week, from 2
9s
to roll back, from 41m
Next project
Design system and marketing site for a payments startup