The document summarizes updates to the Jenkins project since its split from the Hudson project in 2011. It discusses the interim governance board, increased development activity and contributions from the community, initiatives to improve plugin development and testing, and plans for a stable but older release line and logo contest. The project is thriving with more users, developers, and formal governance processes since the split from Hudson.

1. JenkinsProject Update Kohsuke Kawaguchi

2. Divorce Infra issues in java.net led to the question over the control by Oracle (Nov 2010) Trademark was used as a weapon Led to discussion with Oracle offline to transfer the trademark custody to 3rd party foundation Negotiation failed. Vote proposed to rename Hudson to Jenkins (Jan 2011) Subsequently approved by 214-to-14

3. Jenkins Project Since Then http://jenkins-ci.org/ 3 people interim governance board Myself Andrew Bayer from Cloudera Dean Yu from Yahoo In process of … Registering trademark Seeking an umbrella organization for holding assets, CLA, etc.

4. Development in Jenkins Project Most Hudson developers moved to Jenkins 733 commits since the divorce (vs 172) 42% by community (vs 1%) By 48 people (vs 7) More contributions after divorce 170 pull requests (vs 20) 11.3 change log items per release (vs 6.7 before) 94 publicized committers on GitHub (vs 4) 496 repositories (vs 1)

5. Development in Jenkins Project Plugin development moved to Jenkins Showing # of commits in Hudson plugins Of 25 top plugins 21 moved to Jenkins 4 had no commits 40 new plugins since the split (vs 1)

6. Delivering what users need Iterative, compatible improvements over the codebase Changes that actually deliver values to users Just like we’ve been doing all along Bugs/RFEs are getting delivered 282 tickets fixed (vs 68) 514 tickets created (vs 129)

7. Users are following Public Hudson sites moving to Jenkins Apache, JRuby, NASA, Nuxeo, Scala, PiWiki, CreativeCommons, OpenIndiana, … Users list traffic 1280 e-mails (vs 259) Downloads are healthy 8132 war, 2733 deb, 1237 rpm, 1320 zip (per week) OS Distributions are switching Ubuntu, FreeBSD, OpenBSD

8. Users are following

9. New Initiatives Bi-weekly governance meeting Held on IRC, open to everyone Discuss project issues and ideas Minutes open to anyone: http://meetings.jenkins-ci.org/ Turns out very useful in … Getting fresh people into project Creating stronger bonds among developers

10. “Stable But Older” Release Line Main release line The main release line continues as is Each releases goes through all our automated tests Fork a maintenance branch every 3 months from a release Only proven backported fixes from mainline Monthly release Hopefully 1.400.1 in May

11. Goal of “Stable But Older” Release Line Help those who value stability more than new features Slower release cycles, more conservative changes Provide focal point for people doing their own QA Often a team in large company does this

12. Plugin compatibility testing Frederic Camblor is driving this effort Rerun plugin tests against the latest version of Jenkins Should help us catch regressions earlier

13. Plugins in JRuby Charles Lowell is driving this effort Jenkins used more and more in languages like Ruby, PHP, Python Those users would like to write plugins in their languages, not in Java Hopefully attract new wave of plugin developers

14. My Focus in Core Serve plugin developers technically More extension points Better cross-referencing existing plugins Technologies to simplify their code Serve plugin developers socially Hackathons, documentation Restore infrastructure support

15. My Focus in Core Continue housekeeping work Improved modularity Bug fixes, better error diagnostics, smoothing out rough edges Better native packaging Push features along development themes But do so by writing plugins

16. New Logo Contest: Run-off Closes next Monday

17. Conclusion Jenkins project is thriving Users & devs are voting with their feet More formal & transparent governance New initiatives New release model Better plugin compatibility testing Plugin development for other languages

18. Q&A Upcoming Meetups 4/13 San Francisco 5/1 Paris 5/20 Tokyo 5/28 Hamburg Resources http://jenkins-ci.org/ Twitter: @jenkinsci