How CloudBees CI Brings Enterprise Scale to Jenkins
summary
CloudBees CI runs multiple managed controllers so teams get independent Jenkins stacks with central governance, avoiding island sprawl or a brittle monolith. It validates popular plugins, provides pipeline template catalogs and controller templates, and supports Kubernetes agents for ephemeral build capacity. Claims include 70% market share for Jenkins, an Autodesk customer reporting 10× developer productivity, and another customer seeing about a 75% defect reduction after consolidating and templating pipelines.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:23Cloudbees Assurance
- 2:09Goals
- 2:43Eliminating Risks
- 3:13Efficiency
- 3:31Three Unpleasant Truths
- 5:11How Jenkins Tends To Get Started
- 6:17Problem of Hidden Costs
- 8:49To Create a Monolithic Jenkins Server
- 10:26Technical Diversity
- 13:13Templates
- 14:12Case Studies of Cloud Bci Customers
- 21:24An Example of How Templates Can Be Used To Promote Best Practices
- 23:08Pipeline Template Catalogs
related talks
50mJenkins in the Enterprise: Building Resilient CI Infrastructure
38mOperating Jenkins at Scale
11mUsing CloudBees Jenkins Enterprise to Effectively Manage the Jenkins Ecosystem
27mAutomation, Innovation and Continuous Delivery
22mAll Things Jenkins and Cloud Foundry
30mA Journey Introducing Jenkins to Enterprise IT
42mAutomation, Innovation and Continuous Delivery
35mOpening Keynote – Kohsuke Kawaguchi
