Geeks With Blogs

Soppa Group India
iSmart Panache Inc
R Systems Internationals Ltd
Technovate eSolutions Pvt Ltd
The contents of this blog are my personal opinion and do not represent in any way the view of my employer.
These postings are provided "AS IS" with no warranties, and confer no rights.

Google PR™ - Post your Page Rank with

Narendra Tiwari

In my previous posts I discussed about 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:-

Java support on CCNet

Please share your thoughts...


Posted on Sunday, March 28, 2010 5:22 PM .Net | Back to top

Comments on this post: Hudson.. another Continuous Integration tool

# re: Hudson.. another Continuous Integration tool
Requesting Gravatar...
Thanks for infromation about this tool. At my past job we used CCNet. At current job place we are thinking about CCNet too, I didn't know that we can find another good tool for continuous integration, I should to look on it.

Can you provide me with answer about wich tool better? Is Hudson have web interface?
Left by Denis Gladkikh on Mar 28, 2010 9:15 PM

# re: Hudson.. another Continuous Integration tool
Requesting Gravatar...

As I written in the post Hudson provides a very easy interface to configure projects where in CCNet we used to play with a few xml files but thats fine for me.. being techies we should be enough resilient to play with configuration xml files.

My personal experience is to go by CCNet as it has its native support to .Net. and a very nice dashboard we can see our xml reports generated by adhoc tools configured in the build scripts.
Left by Narendra Tiwari on Apr 01, 2010 9:47 PM

Your comment:
 (will show your gravatar)

Copyright © Narendra Tiwari | Powered by: