SlideShare a Scribd company logo

Current state of Jenkins

•
•
Kohsuke Kawaguchi
Kohsuke Kawaguchi

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 of 18
JenkinsProject UpdateKohsuke Kawaguchi
DivorceInfra issues in java.net led to the question over the control by Oracle (Nov 2010)Trademark was used as a weaponLed to discussion with Oracle offline to transfer the trademark custody to 3rd party foundationNegotiation failed. Vote proposed to rename Hudson to Jenkins (Jan 2011)Subsequently approved by 214-to-14
Jenkins Project Since Thenhttp://jenkins-ci.org/3 people interim governance boardMyselfAndrew Bayer from ClouderaDean Yu from YahooIn process of …Registering trademarkSeeking an umbrella organization for holding assets, CLA, etc.
Development in Jenkins ProjectMost Hudson developers moved to Jenkins733 commits since the divorce (vs 172)42% by community (vs 1%)By 48 people (vs 7)More contributions after divorce170 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)
Development in Jenkins ProjectPlugin development moved to JenkinsShowing # of commits in Hudson pluginsOf 25 top plugins21 moved to Jenkins4 had no commits40 new plugins since the split (vs 1)
Delivering what users needIterative, compatible improvements over the codebaseChanges that actually deliver values to usersJust like we’ve been doing all alongBugs/RFEs are getting delivered282 tickets fixed (vs 68)514 tickets created (vs 129)
Users are followingPublic Hudson sites moving to JenkinsApache, JRuby, NASA, Nuxeo, Scala, PiWiki, CreativeCommons, OpenIndiana, …Users list traffic1280 e-mails (vs 259)Downloads are healthy8132 war, 2733 deb, 1237 rpm, 1320 zip (per week)OS Distributions are switchingUbuntu, FreeBSD, OpenBSD
Users are following
New InitiativesBi-weekly governance meetingHeld on IRC, open to everyoneDiscuss project issues and ideasMinutes open to anyone: http://meetings.jenkins-ci.org/Turns out very useful in …Getting fresh people into projectCreating stronger bonds among developers
“Stable But Older” Release LineMain release lineThe main release line continues as isEach releases goes through all our automated testsFork a maintenance branch every 3 months from a releaseOnly proven backported fixes from mainlineMonthly releaseHopefully 1.400.1 in May
Goal of “Stable But Older” Release LineHelp those who value stability more than new featuresSlower release cycles, more conservative changesProvide focal point for people doing their own QAOften a team in large company does this
Plugin compatibility testingFrederic Camblor is driving this effortRerun plugin tests against the latest version of JenkinsShould help us catch regressions earlier
Plugins in JRubyCharles Lowell is driving this effortJenkins used more and more in languages like Ruby, PHP, PythonThose users would like to write plugins in their languages, not in JavaHopefully attract new wave of plugin developers
My Focus in CoreServe plugin developers technicallyMore extension pointsBetter cross-referencing existing pluginsTechnologies to simplify their codeServe plugin developers sociallyHackathons, documentationRestore infrastructure support
My Focus in CoreContinue housekeeping workImproved modularityBug fixes, better error diagnostics, smoothing out rough edgesBetter native packagingPush features along development themesBut do so by writing plugins
New Logo Contest: Run-offCloses next Monday
ConclusionJenkins project is thrivingUsers & devs are voting with their feetMore formal & transparent governanceNew initiativesNew release modelBetter plugin compatibility testingPlugin development for other languages
Q&AUpcoming Meetups 4/13 San Francisco 5/1 Paris 5/20 Tokyo 5/28 HamburgResourceshttp://jenkins-ci.org/ Twitter: @jenkinsci

More Related Content

Current state of Jenkins

  • 2. DivorceInfra issues in java.net led to the question over the control by Oracle (Nov 2010)Trademark was used as a weaponLed to discussion with Oracle offline to transfer the trademark custody to 3rd party foundationNegotiation failed. Vote proposed to rename Hudson to Jenkins (Jan 2011)Subsequently approved by 214-to-14
  • 3. Jenkins Project Since Thenhttp://jenkins-ci.org/3 people interim governance boardMyselfAndrew Bayer from ClouderaDean Yu from YahooIn process of …Registering trademarkSeeking an umbrella organization for holding assets, CLA, etc.
  • 4. Development in Jenkins ProjectMost Hudson developers moved to Jenkins733 commits since the divorce (vs 172)42% by community (vs 1%)By 48 people (vs 7)More contributions after divorce170 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 ProjectPlugin development moved to JenkinsShowing # of commits in Hudson pluginsOf 25 top plugins21 moved to Jenkins4 had no commits40 new plugins since the split (vs 1)
  • 6. Delivering what users needIterative, compatible improvements over the codebaseChanges that actually deliver values to usersJust like we’ve been doing all alongBugs/RFEs are getting delivered282 tickets fixed (vs 68)514 tickets created (vs 129)
  • 7. Users are followingPublic Hudson sites moving to JenkinsApache, JRuby, NASA, Nuxeo, Scala, PiWiki, CreativeCommons, OpenIndiana, …Users list traffic1280 e-mails (vs 259)Downloads are healthy8132 war, 2733 deb, 1237 rpm, 1320 zip (per week)OS Distributions are switchingUbuntu, FreeBSD, OpenBSD
  • 9. New InitiativesBi-weekly governance meetingHeld on IRC, open to everyoneDiscuss project issues and ideasMinutes open to anyone: http://meetings.jenkins-ci.org/Turns out very useful in …Getting fresh people into projectCreating stronger bonds among developers
  • 10. “Stable But Older” Release LineMain release lineThe main release line continues as isEach releases goes through all our automated testsFork a maintenance branch every 3 months from a releaseOnly proven backported fixes from mainlineMonthly releaseHopefully 1.400.1 in May
  • 11. Goal of “Stable But Older” Release LineHelp those who value stability more than new featuresSlower release cycles, more conservative changesProvide focal point for people doing their own QAOften a team in large company does this
  • 12. Plugin compatibility testingFrederic Camblor is driving this effortRerun plugin tests against the latest version of JenkinsShould help us catch regressions earlier
  • 13. Plugins in JRubyCharles Lowell is driving this effortJenkins used more and more in languages like Ruby, PHP, PythonThose users would like to write plugins in their languages, not in JavaHopefully attract new wave of plugin developers
  • 14. My Focus in CoreServe plugin developers technicallyMore extension pointsBetter cross-referencing existing pluginsTechnologies to simplify their codeServe plugin developers sociallyHackathons, documentationRestore infrastructure support
  • 15. My Focus in CoreContinue housekeeping workImproved modularityBug fixes, better error diagnostics, smoothing out rough edgesBetter native packagingPush features along development themesBut do so by writing plugins
  • 16. New Logo Contest: Run-offCloses next Monday
  • 17. ConclusionJenkins project is thrivingUsers & devs are voting with their feetMore formal & transparent governanceNew initiativesNew release modelBetter plugin compatibility testingPlugin development for other languages
  • 18. Q&AUpcoming Meetups 4/13 San Francisco 5/1 Paris 5/20 Tokyo 5/28 HamburgResourceshttp://jenkins-ci.org/ Twitter: @jenkinsci