For Continuous Integration Should I Use a Jenkin or Hudson?

by Ruth Evans SEO

So many are getting Confused in Choosing Whether Jenkin or Hudson for Continuous Integration. Here is the solution for this and it is only according to my View only. If any mistake is there means Please Let me Know So that i will Correct it.

When the Jenkins/Hudson divorce came about, most of the Hudson developers (including, crucially, the original creator of the project, Kohsuke Kawaguchi) moved on to Jenkins.

Since the split, Jenkins has the most work, most commits, better community, better plugins, and so on.

Hudson is tied to Oracle and its corporate infrastructure. The project will attempt to go a more "enterprise" route, with fewer releases but more testing and an emphasis on backward compatibility, possibly more Eclipse integration. If your project is in a more corporate environment, a case could be made that you should use Hudson.

Otherwise, stick with (or upgrade to) Jenkins. This is what the majority of the community is moving to.