Thursday, October 27, 2011

Hudson or Jenkins for me?

We have been faced with the choice of going with Hudson or Jenkins as our CI enviroment for our ADF build.

Hudson
Oracle backed Sonatype supported. More structured.


Jenkins
More OSS style, larger comunity majority of the orginal developer community.

Really very similar.

Guess the safest thing to do is go with Hudson and upgrade to Jenkins if need be. So we will be going with Hudson, head decision not heart decision. This is also consistent with the ADF community.



Links :http://jaxenter.com/oracle-speak-out-on-hudson-jenkins.1-34569.html
http://bobbickel.blogspot.com/2011/03/jenkins-vs-hudson-time-to-upgrade.html
http://jenkins-ci.org/content/about-jenkins-ci
http://hudson-ci.org/docs/process_summary.html
http://groups.google.com/group/adf-methodology/browse_thread/thread/f4c4f616d5520166?pli=1

4 comments:

  1. How is Hudson working for you?

    Was it the right decision?

    ReplyDelete
  2. Hudson does everything we need it to, I am not to fond of the caching refreshing issues that I am having with it (to use Teamcity again would be great) but all in all so far so good.

    ReplyDelete
  3. Look here.

    http://adfpractice-sokol.blogspot.com/2012/06/adf-application-jenkins-websphere.html

    ReplyDelete