• Save
Current state of Jenkins
Upcoming SlideShare
Loading in...5

Current state of Jenkins



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

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



Total Views
Views on SlideShare
Embed Views



27 Embeds 2,337

http://jenkins-ci.org 2081
http://fuzz-box.blogspot.com 155
http://www.slideshare.net 25
http://fuzz-box.blogspot.in 15
http://fuzz-box.blogspot.gr 9
url_unknown 8
http://fuzz-box.blogspot.co.uk 6
http://fuzz-box.blogspot.ca 4
http://fuzz-box.blogspot.fr 4
http://fuzz-box.blogspot.de 4
https://twitter.com 3
http://feeds.feedburner.com 3
http://translate.googleusercontent.com 2
http://fuzz-box.blogspot.com.es 2
http://fuzz-box.blogspot.be 2
http://twitter.com 2
http://fuzz-box.blogspot.se 2
http://fuzz-box.blogspot.ro 1
http://google.com 1
http://fuzz-box.blogspot.co.at 1
http://fuzz-box.blogspot.sg 1
http://fuzz-box.blogspot.com.br 1
http://fuzz-box.blogspot.pt 1
http://fuzz-box.blogspot.com.au 1
http://fuzz-box.blogspot.co.il 1
http://paper.li 1
http://fuzz-box.blogspot.ie 1


Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • 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?
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Current state of Jenkins Current state of Jenkins Presentation Transcript

  • JenkinsProject Update
    Kohsuke Kawaguchi
  • 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
  • Jenkins Project Since Then
    3 people interim governance board
    Andrew Bayer from Cloudera
    Dean Yu from Yahoo
    In process of …
    Registering trademark
    Seeking an umbrella organization for holding assets, CLA, etc.
  • 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)
  • 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)
  • 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)
  • 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
  • Users are following
  • 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
  • “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
  • 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
  • Plugin compatibility testing
    Frederic Camblor is driving this effort
    Rerun plugin tests against the latest version of Jenkins
    Should help us catch regressions earlier
  • 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
  • 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
  • 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
  • New Logo Contest: Run-off
    Closes next Monday
  • 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
  • Q&A
    Upcoming Meetups
    4/13 San Francisco
    5/1 Paris
    5/20 Tokyo
    5/28 Hamburg
    Twitter: @jenkinsci