GitLab Shared Runners: Fair CI Capacity, and the Cache That Lies
How GitLab.com scaled CI with shared runners, isolation, and caching — and why a cache hit that skips a compile can still ship the wrong artifact.
Tag
10 articles · 39 min of reading
How GitLab.com scaled CI with shared runners, isolation, and caching — and why a cache hit that skips a compile can still ship the wrong artifact.
Humble and Farley's core ideas — trunk-based work, stop-the-line, deploy the same artifact — translated into GitHub Actions and Kubernetes without the theater.
What SLSA levels actually require, how provenance attestations fit next to SBOMs, and a realistic path from 'we tag git' to a verifiable builder.
A concrete comparison of blue-green and canary deployment strategies, including the infrastructure they each require and where one clearly beats the other.
How GitOps replaces imperative deploy scripts with a reconciled, auditable source of truth, and the practical patterns for running it well with Argo CD or Flux.
How trunk-based development and merge queues reduce integration pain compared to long-lived feature branches, and what they require to work in practice.
Practical caching techniques for CI pipelines, from dependency caches to Docker layer caches, and how to avoid the stale-cache bugs that undo the savings.
How Shopify keeps a single large Rails monolith deployable dozens of times daily using merge queues, canaries, and fast automated rollback.
How Docker's layer cache actually works under the hood, and the Dockerfile patterns that keep builds fast instead of quietly rebuilding everything.
A bundle size budget that isn't enforced in CI is a suggestion, and suggestions don't survive contact with a deadline — here's how to make it stick.