Fog Creek Software
Discussion Board




Draco.NET vs. CruiseControl.NET

Hi All,

This weekend I'm planning on setting up a Continuous Integration server. I'm going to setup NAnt and NUnit, and either Draco.NET () or CruiseControl.NET (). This will be the first time that I've used any of these utilities, so I'd appreciate any tips, comments, suggestions about them (or if there's something better, that too).

I'm going to ask about reccomendations between CVS and Subversion in a seperate thread.

The differences between Draco.NET and CC.NET aren't really clear to me. Draco was patterned after CruiseControl, which makes me wonder if there was something in CC.NET that they wanted to imrove upon, or if maybe Draco was started before the .NET port of CC was released.

Does anyone have any experience with either or both? Are there any others that I should consider (Open or Commercial, I'll consider all - although I'm using these to develop closed source apps, in case that may conflict with the license of an Open app)?

Thanks for the help,

  --Josh

JWA
Thursday, September 18, 2003

I forgot to paste the links to the two products after their names, here they are:

http://draconet.sourceforge.net/

http://ccnet.thoughtworks.com/

Also, in case the .NET doesn't give it away, I'll be using these on an XP PRO or Win2003 box.

  --Josh

JWA
Thursday, September 18, 2003

Haven't used continuous integration yet. I'm intreaged by it though, but I can not see the real benefits for me at the moment (small team, short build times). You can also add Hippo.NET http://hipponet.sourceforge.net/ to your list.

Just me (Sir to you)
Friday, September 19, 2003

I spent a few hours this week trying to set both of these up.

I got closest with Draco.Net, but gave up when the config file I ended up with caused the server to exit immediately and silently.

CC.Net came up short when it wanted to use an the version of nant it was bundled with.  My build uses an older version with some custom tasks.  I tried to upgrade to the new version but found that the new <cl > task didn't work with empty <sources ...> filesets (I use the @<files> option to provide the list of source files since having a hundred plus source files on the command line caused problems in the past).

I will probably take another look at Draco.Net when I have a few hours to spare.

The main benefit I want is the ability for my FULL unit test suite to be run automatically whenever I commit a batch of changes.

The full suite is just too long to be testing with during the development cycle.

Rob Walker
Friday, September 19, 2003

I haven't used the .NET version but the original CC works great for me.

CC lover
Friday, September 19, 2003

*  Recent Topics

*  Fog Creek Home