How we scale DroneCI on demand
summary
OwnCloud replaces Travis and Jenkins with a container-native Drone setup, deploys infrastructure with Terraform and Ansible, and adds a separate drone autoscaler that launches up to 50 cloud agents on AWS/DigitalOcean/GCE/Hetzner on demand. Build queue time drops to ~25–30 minutes for feedback while cumulative CPU time grows; CI stores ~200 GB of artifacts. Agents spin up and deregister automatically, costing roughly €250/month for 50 parallel instances, and enables local reproduction via Docker-based pipeline steps.
AI-written summary · about
chapters (15)
- 0:00Introduction and speakers
- 1:47About ownCloud and challenges
- 4:19Old CI infrastructure pains
- 9:55Introducing Drone CI
- 13:30Migration to Drone CI
- 16:45Limitations and improvements
- 17:53Drone autoscaler setup
- 20:26Build time improvements
- 22:13Current setup and results
- 23:18Lessons learned and feedback
- 26:49Production challenges
- 27:52Infrastructure scaling tips
- 29:00Q&A part 1
- 33:21Q&A part 2
- 35:03Future improvements
related talks
31m"How We Fired Our Butlers: Drone CI at Scale"
34mContinuous Container Integration for Containers
38mContinuous deployment at Skyscanner
36mCI/CD BoF: Delivering Quality Quickly
35mJenkins Scaling and Organization for an Efficient CI
05mCI/CD doesn't necessarily mean Jenkins
22mA Crawl, Walk, Run Story of CI/CD
26mFaster, Cheaper, Leaner: Horizontally Scaling a CI Pipeline