We rebuilt the deploy pipeline from scratch. Here's what changed.
After two years of patching the old queue-based runner, we tore it out. The new pipeline is built around immutable build artifacts, parallel region rollouts, and a typed event stream you can subscribe to. Median deploy time dropped from 3m40s to 47s. Happy to answer specifics below.
- PJplatform-jonas3 hours ago
The parallel region rollout is the unsung hero. We run across seven regions and the old pipeline did them sequentially. Now we get the whole fleet in under 90 seconds with automatic health-gated promotion.
- SCsrechris3 hours ago
Immutable artifacts are a game changer for rollback. Every deploy ID maps to a signed tarball we can re-promote instantly. No more 'rebuild from main and hope the dependencies haven't drifted' at 2am.
- DPdx-priya2 hours ago
The typed event stream deserves more attention. We plug it straight into our ChatOps bot so every 'build started / gate passed / canary healthy / fully promoted' event is first-class data. No more regex-scraping log lines to figure out where a deploy is.