Continuous Integration at Scale on Kubernetes [B]
summary
eBay runs a CIaaS on Kubernetes that does roughly 10,000 builds a day (≈300k/month) by provisioning Jenkins via a CIConfig CRD and a controller that creates PVC-backed Jenkins masters, services and ingress, while builder pods spawn through the Jenkins Kubernetes plugin. Builders use hostPath Maven caches and separate node pools for masters and builders. A hibernation flag tears down pods and services but preserves PVs and ingress to reclaim resources for the 60% of CIs that are idle.
AI-written summary · about
chapters (12)
- 0:00Intro
- 2:23eBay Infrastructure
- 3:22eBay Applications
- 4:11Our Cl Journey
- 6:49Architecture
- 9:56Why CIConfig?
- 11:06CIConfig & Control Loop
- 14:33Life of a Build
- 17:53Ingress
- 20:33Hibernation
- 22:55Learnings
- 25:03Future Work
related talks
35mJenkins Scaling and Organization for an Efficient CI
13mEvolution of containers in continuous integration
42mJenkins X, Continuous Delivery for Kubernetes
43mInfinite Space for Your Tests
39mKubernetes – Infinite Space for Your Tests
35mOff the Beaten Path: An Explorer’s Guide to Kubernetes
05mJenkins in the Cloud
50mContinuous Deployment With Jenkins X And Kubernetes