Why we provisioned 37 Jenkins servers...
summary
A platform team provisions 37 Jenkins servers (one per team/environment) plus Artifactory and a ServiceNow-integrated portal, automates VM provisioning, and ships an onboarding kit and shared build scripts. The claim: isolating teams gives flexibility, resiliency and supportability so developers get push-button deploys while operations retains control. Deploy time drops from hours to minutes, adoption scales across a 10,000+ employee insurer, and after two years the distributed, non‑optimized toolset proves successful. build once deploy many
AI-written summary · about
chapters (15)
- 0:00Intro
- 2:08COMPANY BACKGROUND
- 3:01SDLC
- 4:47APPLICATION DEPLOYMENT VISION
- 5:43TYPICAL CICD ARCHITECTURES
- 7:18PROCESS: OVERALL STRATEGY
- 8:34PROCESS: BUILD
- 9:26PROCESS: DEPLOY
- 12:52MULTI-TEAM BUILD & DEPLOY
- 14:44WHY... EXPLAINED
- 15:10FLEXIBILITY
- 16:19RESILIENCY
- 18:13ADOPTION ACCELERATOR
- 19:22SUPPORTABILITY
- 22:04LESSONS LEARNED
related talks
37mHelping Enterprises Scale Their Jenkins Software Practices and Tools
30mA Journey Introducing Jenkins to Enterprise IT- 30mA Journey Introducing Jenkins to Enterprise IT
33mMaking Strides towards Enterprise-Scale DevOps...w/ Jenkins in Your Tool Chain
28mGrowing Pains - Scaling Jenkins in the Federal Sector
45mBuilding Your Continuous Delivery Toolkit
35mJenkins Scaling and Organization for an Efficient CI
44mFrom Zero to Federated at the Speed of Jenkins