Growing Pains - Scaling Jenkins in the Federal Sector
summary
Federal agency moves 180 projects and 500 users onto Jenkins, running 2,000+ job executions/day with a 7‑person ops team; architecture uses a Jenkins master with 40–50 active slaves and ~124 executors, and yields three next‑gen projects with automated deployments. Slave provisioning is automated via Docker images and the Swarm plugin to auto‑register and tag nodes; job/config XML is versioned in Subversion, LDAP groups plus the Role Strategy plugin enforce access, and labels route builds to capable slaves.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:59Who we serve
- 1:59Backdrop
- 3:26Where we are now
- 4:40How did we get there?
- 5:04Best practices
- 8:02Introducing Jenkins Labels
- 9:46Labels in practice
- 11:50Prepare yourselves
related talks
37mHelping Enterprises Scale Their Jenkins Software Practices and Tools
22mAll Things Jenkins and Cloud Foundry
34mHelping Enterprises Scale Their Jenkins Software Practices and Tools
35mJenkins Scaling and Organization for an Efficient CI
41mScaling Jenkins
55mContinuous Integration on Steroids
01h 01mOpening Keynote
27mWhy we provisioned 37 Jenkins servers...