In my previous posts I discussed about Cruisecontrol.net and its legacy support to .Net development.

Hudson  is yet another continuous integration tool. Hudson is also free like CCNet and built in java.

- CCNet has its legacy support to .Net applications where as Hudson can be easily configured on both the environments (.Net and Java).

- One of the major differences in CCNet and Hudson is the richer GUI of Hudson provide user interactive screens for project configuration where as in CCNet we have to play with a few xml configuration files.

Both the tools are capable of providing basic features of continuous integration e.g.:-

- Source Control configuration
- Code Compilation/Build
- Ad hoc plugin tools to be configured along with compilation

Support for adhoc tools seems to be bigger with CCNet e.g. There are almost every source control plugin available with CCNet where as Hudson has support for limited source control servers.

Basically there is an interseting point to see is that there are 2 major partsof whole CI system one performed by build tool and rest. Build tool takes care of all adhoc plugin tools  so no matter if CI tool does not have plugin for that tool if thet tools provides command line support that can be configured in build tool and that build tool is then configured with CI tool inturn. For example if I have a build script configured in MSBuild and CCNet can be easily switched to Hudson. Here we need not to change anything in build script we just need to configure MSBuild on Hudson and pass the path of script file and thats it... all is same.

Hudson Resources:-
- https://hudson.dev.java.net/
- http://wiki.hudson-ci.org/display/HUDSON/Meet+Hudson
- http://wiki.hudson-ci.org/display/HUDSON/Plugins
- http://callport.blogspot.com/2009/02/hudson-for-net-projects.html

Java support on CCNet
http://confluence.public.thoughtworks.org/display/CC/Getting+Started+With+CruiseControl?focusedCommentId=19988484#comment-19988484

Please share your thoughts...