How we made the Jenkins community

" summary

Describes how the Jenkins CI project grew from a solo spare‑time effort into a large community with 300–550+ independently developed plugins by focusing on technical extensibility and low-friction onboarding. Covers concrete community-building ingredients—making the system extensible so contributors aren’t blocked and minimizing the steps required before someone can start hacking.

AI-written summary · about

" related talks

• 45mBuilding Your Continuous Delivery ToolkitT.J. Randall · Jenkins User Conference Boston 2014
• 42mSeven Habits of Highly Effective Jenkins UsersAndrew Bayer · Jenkins User Conference San Francisco 2014
• 42mBuilding Your Continuous Delivery ToolkitAndrew Phillips · Jenkins User Conference Europe 2014 Berlin
• 14mHow we manage over1500 git repo’s CI/CD with a full InnerSource solutionGaël Selig · InnerSource Summit 2023
• 27mWhy we provisioned 37 Jenkins servers...Alicia Davis · DevOpsDays Boston 2018
• 28mGrowing Pains - Scaling Jenkins in the Federal SectorBrian Patterson · Jenkins User Conference U.S. East 2015
• 35mOptimizing Your CI: Lessons Learned from a Successful Jenkins RebuildJonathann Zenou · Jenkins User Conference U.S. East 2015
• 43mSeven Habits of Highly Effective Jenkins UsersAndrew Bayer · Jenkins User Conference Europe 2014 Berlin