JenkinsProject Update<br />Kohsuke Kawaguchi<br />
Divorce<br />Infra issues in java.net led to the question over the control by Oracle (Nov 2010)<br />Trademark was used as...
Jenkins Project Since Then<br />http://jenkins-ci.org/<br />3 people interim governance board<br />Myself<br />Andrew Baye...
Development in Jenkins Project<br />Most Hudson developers moved to Jenkins<br />733 commits since the divorce (vs 172)<br...
Development in Jenkins Project<br />Plugin development moved to Jenkins<br />Showing # of commits in Hudson plugins<br />O...
Delivering what users need<br />Iterative, compatible improvements over the codebase<br />Changes that actually deliver va...
Users are following<br />Public Hudson sites moving to Jenkins<br />Apache, JRuby, NASA, Nuxeo, Scala, PiWiki, CreativeCom...
Users are following <br />
New Initiatives<br />Bi-weekly governance meeting<br />Held on IRC, open to everyone<br />Discuss project issues and ideas...
“Stable But Older” Release Line<br />Main release line<br />The main release line continues as is<br />Each releases goes ...
Goal of “Stable But Older” Release Line<br />Help those who value stability more than new features<br />Slower release cyc...
Plugin compatibility testing<br />Frederic Camblor is driving this effort<br />Rerun plugin tests against the latest versi...
Plugins in JRuby<br />Charles Lowell is driving this effort<br />Jenkins used more and more in languages like Ruby, PHP, P...
My Focus in Core<br />Serve plugin developers technically<br />More extension points<br />Better cross-referencing existin...
My Focus in Core<br />Continue housekeeping work<br />Improved modularity<br />Bug fixes, better error diagnostics, smooth...
New Logo Contest: Run-off<br />Closes next Monday<br />
Conclusion<br />Jenkins project is thriving<br />Users & devs are voting with their feet<br />More formal & transparent go...
Q&A<br />Upcoming Meetups<br />	4/13 San Francisco<br />	5/1   Paris<br />	5/20 Tokyo<br />	5/28 Hamburg<br />Resources<br...
Upcoming SlideShare
Loading in...5
×

Current state of Jenkins

12,445

Published on

After a few months of rename, Jenkins project is thriving --- here are some numbers.

Published in: Technology, Art & Photos
1 Comment
4 Likes
Statistics
Notes
  • Hi Kohsuke,

    We are working with Hudson and we are evaluating Jenkins. But My question is, why should we move to Jenkins? All the plugins which we neeeded are there in Hudson. Also, we dont upgrade the Hudson version frequently. Is Jenkins perform better than Hudson?
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
12,445
On Slideshare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
0
Comments
1
Likes
4
Embeds 0
No embeds

No notes for slide

Current state of Jenkins

  1. 1. JenkinsProject Update<br />Kohsuke Kawaguchi<br />
  2. 2. Divorce<br />Infra issues in java.net led to the question over the control by Oracle (Nov 2010)<br />Trademark was used as a weapon<br />Led to discussion with Oracle offline to transfer the trademark custody to 3rd party foundation<br />Negotiation failed. Vote proposed to rename Hudson to Jenkins (Jan 2011)<br />Subsequently approved by 214-to-14<br />
  3. 3. Jenkins Project Since Then<br />http://jenkins-ci.org/<br />3 people interim governance board<br />Myself<br />Andrew Bayer from Cloudera<br />Dean Yu from Yahoo<br />In process of …<br />Registering trademark<br />Seeking an umbrella organization for holding assets, CLA, etc.<br />
  4. 4. Development in Jenkins Project<br />Most Hudson developers moved to Jenkins<br />733 commits since the divorce (vs 172)<br />42% by community (vs 1%)<br />By 48 people (vs 7)<br />More contributions after divorce<br />170 pull requests (vs 20)<br />11.3 change log items per release (vs 6.7 before)<br />94 publicized committers on GitHub (vs 4)<br />496 repositories (vs 1)<br />
  5. 5. Development in Jenkins Project<br />Plugin development moved to Jenkins<br />Showing # of commits in Hudson plugins<br />Of 25 top plugins<br />21 moved to Jenkins<br />4 had no commits<br />40 new plugins since the split (vs 1)<br />
  6. 6. Delivering what users need<br />Iterative, compatible improvements over the codebase<br />Changes that actually deliver values to users<br />Just like we’ve been doing all along<br />Bugs/RFEs are getting delivered<br />282 tickets fixed (vs 68)<br />514 tickets created (vs 129)<br />
  7. 7. Users are following<br />Public Hudson sites moving to Jenkins<br />Apache, JRuby, NASA, Nuxeo, Scala, PiWiki, CreativeCommons, OpenIndiana, …<br />Users list traffic<br />1280 e-mails (vs 259)<br />Downloads are healthy<br />8132 war, 2733 deb, 1237 rpm, 1320 zip (per week)<br />OS Distributions are switching<br />Ubuntu, FreeBSD, OpenBSD<br />
  8. 8. Users are following <br />
  9. 9. New Initiatives<br />Bi-weekly governance meeting<br />Held on IRC, open to everyone<br />Discuss project issues and ideas<br />Minutes open to anyone: http://meetings.jenkins-ci.org/<br />Turns out very useful in …<br />Getting fresh people into project<br />Creating stronger bonds among developers<br />
  10. 10. “Stable But Older” Release Line<br />Main release line<br />The main release line continues as is<br />Each releases goes through all our automated tests<br />Fork a maintenance branch every 3 months from a release<br />Only proven backported fixes from mainline<br />Monthly release<br />Hopefully 1.400.1 in May<br />
  11. 11. Goal of “Stable But Older” Release Line<br />Help those who value stability more than new features<br />Slower release cycles, more conservative changes<br />Provide focal point for people doing their own QA<br />Often a team in large company does this<br />
  12. 12. Plugin compatibility testing<br />Frederic Camblor is driving this effort<br />Rerun plugin tests against the latest version of Jenkins<br />Should help us catch regressions earlier<br />
  13. 13. Plugins in JRuby<br />Charles Lowell is driving this effort<br />Jenkins used more and more in languages like Ruby, PHP, Python<br />Those users would like to write plugins in their languages, not in Java<br />Hopefully attract new wave of plugin developers<br />
  14. 14. My Focus in Core<br />Serve plugin developers technically<br />More extension points<br />Better cross-referencing existing plugins<br />Technologies to simplify their code<br />Serve plugin developers socially<br />Hackathons, documentation<br />Restore infrastructure support<br />
  15. 15. My Focus in Core<br />Continue housekeeping work<br />Improved modularity<br />Bug fixes, better error diagnostics, smoothing out rough edges<br />Better native packaging<br />Push features along development themes<br />But do so by writing plugins<br />
  16. 16. New Logo Contest: Run-off<br />Closes next Monday<br />
  17. 17. Conclusion<br />Jenkins project is thriving<br />Users & devs are voting with their feet<br />More formal & transparent governance<br />New initiatives<br />New release model<br />Better plugin compatibility testing<br />Plugin development for other languages<br />
  18. 18. Q&A<br />Upcoming Meetups<br /> 4/13 San Francisco<br /> 5/1 Paris<br /> 5/20 Tokyo<br /> 5/28 Hamburg<br />Resources<br />http://jenkins-ci.org/<br /> Twitter: @jenkinsci<br />

×