Logistics
Orbital Freight got their monorepo pipeline under 8 minutes
120 packages, every one rebuilding on every push, until affected-target detection was configured correctly.
120 → 5
Packages built
45m → 8m
Pipeline
−62%
CI spend
“We had Nx the whole time. We just had fetch-depth set to 1, so it could never tell what changed.”
Orbital had adopted Nx two years earlier and never seen the benefit, because a shallow checkout meant affected detection had no base to compare against and silently fell back to building everything.
The fix
- fetch-depth set to 0 so affected detection works
- Nx remote caching enabled so CI and developers share artefacts
- Task graph run on one 32 vCPU runner rather than many small ones
- A full build retained on main as a safety net
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
Northwind LabsA Rust monorepo with a 40-minute cold build, brought under control with sccache and native arm64 runners.HarboursideA regulated fintech that needed builds, cache and logs inside the EU, without operating a runner fleet.Kestrel MobileAn iOS team paying for macOS minutes to run JavaScript tests, and what moving them to Linux did.