I'm an Agile and Lean Strategist specialised in coaching and managing the transformation of IT departments, from startups to enterprise-scale organisations, to highly efficient, productive and energised environments. I also have experience as senior development manager and architecture governance in large enterprises, especially in the finance sector. Marco is a DZone MVB and is not an employee of DZone and has posted 26 posts at DZone. You can read more from them at their website. View Full User Profile

Hudson vs Jenkins CI?

  • submit to reddit

After recent disagreements between Oracle from one side and Hudson creators and open community on the other, the latter decided that Hudson was to be forked and become Jenkins CI. More details can be found here and here.

Now Jenkins CI has got a life of his own and so does Hudson. However, while the former is the continuation of the original Hudson open source project, under the original creator and towards an open-source future (at least we think), the latter is now under Oracle's wing with more structure around it. Oracle realised the commercial opportunity that the vast Hudson user base represented; so did Sonatype which has started to work towards a professional (e.g. commercial) version of Hudson, to be targeted to enterprises with over 1,000 employees. The webinar in which Sonatype explains its roadmap for Hudson can be found here (the link is active at the time of writing).

Sonatype intends to do with Hudson what it has already done with Nexus, with the difference that Hudson was not an invention of Sonatype. My question is: should Sonatype have invested in Jenkins CI over Hudson? It is true that Hudson might have more enterprise focus because of Oracle's support, but at the same time it appears as if the original Hudson users are moving towards Jenkins CI. In the end, migrating to Jenkins CI from Hudson might be as simple as switching and renaming a war file.

Why didn't Sonatype choose Jenkins CI over Hudson? My view is that the choice was not dictated by professional or technical reasons, but rather by bad timing.

What would happen to Hudson, and by reflection to Hudson professional, if the majority of users moved to Jenkins CI?

Of the two runners, my view is that Jenkins CI will win the competition over Hudson and my reasons are simple: Jenkins CI lives in the original spirit which originated Hudson; the creator of Hudson, Kohsuke Kawaguchi, is the leader of the new Jenkins CI movement; finally,  the activity around the new Jenkins CI seems frantic, at least judging by the posts on Twitter and the blogs out there.

Happy technology.


From http://tedone.typepad.com/blog/2011/03/hudson-vs-jenkins-ci.html

Published at DZone with permission of Marco Tedone, author and DZone MVB.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)


Christian Beute... replied on Fri, 2011/03/25 - 4:03am

That is the question of the hour.

I'm still not sure who will win that race, and would be happier if Sonatype would jump on the Jenkins trail, or at least vote for longterm compatibility of Jenkins and Hudson ..


Alan Parkinson replied on Fri, 2011/03/25 - 4:49am

I agree with the author about Sonatype's timing appearing to be bad, but was it Sonatype's interest in Hudson that made Oracle see the business opportunity and act?

My personal opinion is both will be around for quite sometime but I think Jenkins will have the edge due to the plugin ecosystem, and it seems many of the plugin maintainers have moved away from Hudson and only support Jenkins. This leaves Sonar and Oracle with a shrinking ecosystem and a number of plugins that will need support.

I think the range of plugins available in the ecosystem has made Hudson successful as it can cope with many situations, and anyone who can do this better will win in the long term.

Damien Lepage replied on Fri, 2011/03/25 - 8:53am

I thought Sonatype jumped on Hudson after Jenkins was launched, seeing a business opportunity in taking the lead of Hudson. So, is it a bad timing or a smelly opportunism?

Marco Tedone replied on Fri, 2011/03/25 - 9:12am in response to: Damien Lepage

You are right, Damien, Jenkins had already been branched at the time Sonatype jumped on Hudson. I think that this will not be a business opportunity for Sonatype, especially if all current users will move to Jenkins CI.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.