"How We Fired Our Butlers: Drone CI at Scale"
summary
Meltwater runs Drone as an internal service with 1,466 repositories, ~1,200 pipelines/day and about 222 active users, replacing Jenkins, Travis and Circle. Autoscaling agents yield 7 seconds average startup and handled a burst by creating 54 agents for 84 jobs in under 3 minutes. Built features include a path-changed conversion extension to run different pipelines per folder, Docker registry and cache plugins to speed builds, a Drone CLI for local testing, and IAM-based Terraform deployment automation.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:33What is Meltwater?
- 2:58What is Foundation?
- 4:10Outline
- 4:27Replacing CI/CD services with Drone
- 10:01What is Drone?
- 13:34Running Drone: Autoscaler
- 15:54Retiring Jenkins: Why?
- 17:24Retiring Jenkins: Terraform
- 18:10Retiring Jenkins: Marathon
- 18:53Ways The Butler Fought Back
- 19:22Drone Conversion Extensions
- 19:56Paths Changed Extension
- 25:32How we got developers attention
- 29:36Lessons Learned
- 30:51Meltwater Engineering Blog
related talks
37mHow we scale DroneCI on demand
27mScaling to Meet Today's Software Delivery Workloads
54mDevOps in Real Life, A How-To
38mContinuous deployment at Skyscanner
36mCI/CD BoF: Delivering Quality Quickly
22mA Crawl, Walk, Run Story of CI/CD
43mDevOps for Mere Mortals
40mThe Butler Did It: Putting Jenkins To Work For You