Scaling to Meet Today's Software Delivery Workloads
summary
Meltwater runs Drone as a service since June 2018, executing about 1,000–1,300 pipelines per weekday backed by MySQL (not sqlite). Runners intentionally set to capacity=1 for predictability; an autoscaler keeps a 4‑agent minimum and reliably spikes above 70 runners for cron-driven tests. Teams build plugins (popular caching plugin) and a conversion extension paths changed to include/exclude steps. Docker Hub rate limits are solved by injecting auth into agents via cloud‑init so runner containers pull successfully.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:51Why should you listen to me
- 2:42What this talk is about
- 6:40Database
- 8:21Docker Runner
- 9:48Plural Runner
- 10:46Autoscaling
- 17:57Architecture diagram
- 19:54Conversion extensions
- 25:28Outro
related talks
31m"How We Fired Our Butlers: Drone CI at Scale"
54mDevOps in Real Life, A How-To
37mHow we scale DroneCI on demand
27mDesigning Your Pipelines for Scalability and Resiliency
29mScaling Spinnaker for multi-region multi-cloud SaaS deployments
38mContinuous deployment at Skyscanner
43mFast and Furious: Startup scaling with Kubernetes
48mScaling a Migration to CD at Airbnb