Comments on: Continuous Integration resources

By: Ade

Ade — Fri, 16 May 2008 21:59:16 +0000

Karl,

Just to be clear we’re currently using CC.NET but are evaluating moving to VSTS 2008’s Team Build as we spin up new projects on 2008.

There are some features I’d really like to try out, notably the drop management features.

Thanks,

Ade

By: Karl Metivier

Karl Metivier — Fri, 16 May 2008 19:13:24 +0000

I find very interesting that you, as a Microsoft dev team, choose CC.Net for small projects rather than VSTS. As you point out, VSTS may be more useful for a larger project.

Do you know that the ThoughtWorks team did a CruiseControl in Ruby. It seems very easy to configure your build script that way than in XML. Here is the link:
http://cruisecontrolrb.thoughtworks.com/

Also, thank you for your speeches in Quebec; they were very good and inspiring!

By: Ade

Ade — Wed, 14 May 2008 18:01:32 +0000

I have looked at CI factory briefly. We’ve not used it at p&p largely because we sort of have an out of the box CI story already. I’ve heard good things about it though.

By: Ryan Anthony

Ryan Anthony — Wed, 14 May 2008 16:10:18 +0000

If you haven’t seen CI Factory by Jay Flowers (http://www.cifactory.org/joomla/) then you definitely need to take a look. It makes CC.NET installation, configuration, and integration with supporting tools incredibly easy.

By: redsolo

redsolo — Wed, 14 May 2008 15:54:27 +0000

I have a guide on how to do continuous integration with C# projects using Hudson. Hudson is a very easy to configure and use CI server.

http://redsolo.blogspot.com/2008/04/guide-to-building-net-projects-using.html

By: Ryan Conrad

Ryan Conrad — Tue, 13 May 2008 16:26:51 +0000

A lot of useful information, thank you.

I would also like to point out a useful configuration editor for CruiseControl.NET that can make set up even easier. http://codeplex.com/ccnetconfig