What I learned about teams from building the Jenkins project
summary
Built Jenkins as a plugin-driven CI system that now reaches 300,000 installations and thousands of contributors, the project uses plugins all the way down and a committer-by-hand-raise policy (no gatekeeper code reviews) to give clear ownership and minimize coordination. That yields many competing plugins, natural selection, and surprises like the popular weather icon plugin. Lessons carried into CloudBees: pair for ZerotoOne launches, spotlight motivated teams, and deliberate slack for immature projects preserves innovation while larger teams need more alignment.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:28Open sourcing Java EE
- 5:23Open source contributions
- 7:32Jenkins community design
- 12:11From open source to corporate
- 16:06Control vs autonomy
- 19:18Team ownership
- 21:02Alignment challenges
- 26:19Chaos versus control
- 27:24Team dynamics improvement
- 27:45Q&A
- 28:06Q&A
- 28:50Q&A
- 29:13Q&A
- 30:58Closing
related talks
51mA Conversation on Culture: Our Journey
30mA Journey Introducing Jenkins to Enterprise IT
34mHelping Enterprises Scale Their Jenkins Software Practices and Tools
29mJenkins 2022 and Beyond?
42mAutomation, Innovation and Continuous Delivery- 30mA Journey Introducing Jenkins to Enterprise IT
32mAccelerating Collaborative Plugin Development
39mContinuously Improving Culture through Design Decisions