For Continuous Integration Should I Use a Jenkin or Hudson?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

For Continuous Integration Should I Use a Jenkin or Hudson?

NareshKumar
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.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b8b7d9d8-7903-4730-9b67-a63d92df9cb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: For Continuous Integration Should I Use a Jenkin or Hudson?

jxpearce
The Jenkins Users list might be a better place for this question, but since you asked I can tell you what we're doing.

I'm not sure what you mean by a Corporate Environment. I work for a medium size corporation, 800ish engineers (I think) and we use Jenkins for everything. We choose to manage it ourselves, but Cloudbees offers a managed version if you want that. It's nice to have both options. 

It's also nice that Jenkins is a well run open source project. The main developers seem to be easy to access, and you have a problem with a plugin, you can always submit a PR to fix it yourself.

On Thursday, November 9, 2017 at 9:51:04 PM UTC-8, Naresh K wrote:
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, <a href="https://tekslate.com/jenkins-training" rel="nofollow" link="external" style="font-size:13.44px;color:rgb(85,26,139);font-family:Verdana,Geneva,Helvetica,Arial,sans-serif" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Ftekslate.com%2Fjenkins-training\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGqybnKJcauhbd1ywyjd0BP7M8MKw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Ftekslate.com%2Fjenkins-training\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGqybnKJcauhbd1ywyjd0BP7M8MKw&#39;;return true;">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.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/47cbc371-7452-4d61-add6-bc4c3043e6f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: For Continuous Integration Should I Use a Jenkin or Hudson?

Daniel Beck

> On 10. Nov 2017, at 16:53, [hidden email] wrote:
>
> since you asked

They didn't, this is just spam. Just check where the 'Jenkins' link leads.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/707FEA8B-4938-470B-B983-C020A2D66BE3%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: For Continuous Integration Should I Use a Jenkin or Hudson?

Daniel Beck

> On 10. Nov 2017, at 17:54, Daniel Beck <[hidden email]> wrote:
>
>  this is just spam

And the text is just copied and pasted from a quora.com answer from 2011.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/409E6B7C-4E3C-49F1-BFD5-F1B641A20150%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: For Continuous Integration Should I Use a Jenkin or Hudson?

jxpearce
In reply to this post by Daniel Beck
............................................________ 
....................................,.-'"...................``~., 
.............................,.-"..................................."-., 
.........................,/...............................................":, 
.....................,?......................................................, 
.................../...........................................................,} 
................./......................................................,:`^`..} 
.............../...................................................,:"........./ 
..............?.....__.........................................:`.........../ 
............./__.(....."~-,_..............................,:`........../ 
.........../(_...."~,_........"~,_....................,:`........_/ 
..........{.._$;_......"=,_......."-,_.......,.-~-,},.~";/....} 
...........((.....*~_......."=-._......";,,./`..../"............../ 
...,,,___.`~,......"~.,....................`.....}............../ 
............(....`=-,,.......`........................(......;_,,-" 
............/.`~,......`-...................................../ 
.............`~.*-,.....................................|,./.....,__ 
,,_..........}.>-._...................................|..............`=~-, 
.....`=~-,__......`,................................. 
...................`=~-,,.,............................... 
................................`:,,...........................`..............__ 
.....................................`=-,...................,%`>--==`` 
........................................_..........._,-%.......` 
..................................., 

On Friday, November 10, 2017 at 8:54:23 AM UTC-8, Daniel Beck wrote:

> On 10. Nov 2017, at 16:53, <a href="javascript:" target="_blank" gdf-obfuscated-mailto="2iPS4LAECwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jxpe...@... wrote:
>
> since you asked

They didn't, this is just spam. Just check where the 'Jenkins' link leads.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b572799c-f40b-4811-8b9b-b624336212cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.