Cruise Control is a continues integration software for build and deploy operations. It will check your source control server in defined intervals and will download & compile the projects if there is a modification on them. It will also inform stakeholders about the outcome of the compile. Cruise Control can use other open source projects like NUnit, NAnt, NCover, FXCop and will work with most of the source control servers available.

I will explain the part "how the Cruise Control will work with Subversion". You need to install Subversion first, create a database and some users, use Margus's service wrapper to run Subversion as a Windows server. First, necessary applications you need to instal:

  1. Subversion version 1.1.3
  2. NAnt version 0.85 rc2
  3. NAntContribute version 0.85 rc2
  4. NUnit version 2.2.0
  5. Visual Studio .NET 2003
  6. Notepad2 (to edit XML config files)
  7. TortiseSVN (no need to struggle with command prompt)

NUnit has an easy to use installation. NAnt and NAntContrib is distributed as zip files. Unzip them and copy the NAntContrib/bin folder content into NAnt/bin folder. This way NAnt can use the tasks in NAntContrib. Also add the NAnt/bin folder to Environment Variables/Path so the nant.exe can be called from any directory.

You will be needing IIS as well to check the log records. Make sure that default.aspx is defined as the default document when you create a virtual directory.

I have used .NET Framework 1.1 and build scripts are created based on 1.1 framework. NAntContrib and NAnt versions are important. If they are not the same version, you may not be able to call NAntContrib tasks. NUnit version is also important. It should be 2.2.0 otherwise you need to fiddle with "binding redirections" in test config files.

First of all we will create a C# file that is compilable with NAnt. Once this is working we will hand over everything to Cruise Control. Copy paste the below code into Notepad2 and save it as BestCode.cs into CCExample folder.

        using System;


        namespace KruyzKontrol {

        public class Gurkan


            static void Main(String[] args)


                Console.Write("CC Example is working");




Try with csc if it is compiling successfully. Now, we will create an NAnt build script to compile. Again, copy & paste the below xml script to Notepad2 and save it as into the same folder where your BestCode.cs is.

<?xml version="1.0"?>

<project name="CCExample" default="build" basedir=".">

   <description>any description</description>

   <property name="debug" value="true" />

   <property name="defaultframework" value="net-1.1" />

   <target name="build" description="Compiles the code">

  <csc target="exe" output="BestCode.exe" debug="${debug}">


             <include name="BestCode.cs" />






Open a command prompt to the folder where your BestCode.cs is and enter the NAnt command below. We will test if the NAnt is actually compiling our code.

D:\Workbench\CSharp\Deneme\>nant -t:net-1.1

You should see an output telling you that the compile is successful. If there are errors, check the messages and try to correct them.

NAnt will search for a .build file in the folder and when it found, will compile the source based on the data in the .build file. -t parameter is superseding the old parameter -defaultframework and used to indicate that we want to use Framework version 1.1. Check the outputs and make sure the compile has done. There must be one executable and a debug file (.pdb) in the folder.

Now use TortoiseSVN and send the project to Subversion. I have Subversion working with svn: protocol so I can access to my Subversion server with svn://Yoda or I can use IP address of the machine YODA which is svn:// . Do not forget to create a folder for the project like svn://Yoda/DotNet/CCExample/

Now this is where the pinatas' tail has dropped. We need to get the Cruise Control to do this for us. After you extract the zip of Cruise Control go into the "server" directory. You need to create a file called ccnet.config in this folder containing the xml below. This file will tell the ccnet.exe, what to do.






        <!--<intervalTrigger seconds="30" buildCondition="ForceBuild"/> -->

        <intervalTrigger seconds="30" />


    <sourcecontrol type="svn">

        <!--<executable>c:\program files\subversion\bin\svn.exe</executable>-->








    <build type="nant">



        <buildArgs>"-D:svn.executable=c:\program files\subversion\bin\svn.exe" -t:net-1.1 </buildArgs>














Please refer to the Cruise Control documentation for further explanation. Basically, we have a project that is on Subversion and we want to compile with our NAnt script. We also want all the outputs to be recorded in a log folder.

Create a folder under CruiseControl\Web directory and name it as "log". Find the file web.config under CruiseControl\Web and open with Notepad2. Locate the line below:

<add key="logDir" value="log" />

And change it with this one:

<add key="logDir" value="D:\OpenSource\CruiseControl\web\log\" />

Next step is to create a virtual directory in IIS for the CruiseControl\web folder. You may leave all the default settings but make sure the default.aspx is in the default documents.

Now looks like everything is ready to run the ccnet.exe for our first automated compile\integration. Open a DOS prompt to CruiseControl\server directory and run the ccnet.exe. It will use the ccnet.config file and will check the Subversion to see if there is any change on the project. If there is, it will download the project and compile. Every 30 seconds it will check the Subversion again. To trigger the compile, download the project from Subversion with TortoiseSVN to a different directory and make a change. Send the project back to Subversion with TortoiseSVN and keep an eye on the DOS window that the ccnet.exe running.

It is time to see the outcomes on Internet Explorer. Browse to http://localhost/ccnet/default.aspx.

Another way to be notified about the compiles is CCTray application. It is under CruiseControl/CCTray directory. You may copy this folder to another computer on the network to get notifications about the compiles. Run the CCTray.exe and enter your Cruise Control server URL. You should be able to select your project from the drop down list. My settings are:

Server : tcp://YODA:21234/CruiseManager.rem

Project Name: CCExample

If you are accessing the Cruise Control server from another computer on the network, use the IP address or machine name instead of localhost.

What we have accomplished so far:

  1. Created a project which can be compiled with NAnt.
  2. We have written ccnet.config to get the connection between Cruise Control and Subversion.
  3. CCNet.exe is now controlling the Subversion source control.
  4. When there is a modification on the Subversion, it has been picked up and compiled.
  5. We can see the results from web.
  6. CCTray.exe notifications are working.
What about NUnit Tests

It would be good if we can run the NUnit tests on this project and see the results on Cruise Control web page. You may give a break to ccnet.exe. We will first integrate NAnt and NUnit. When we get a successful test, we will try to see the test results on Cruise Control.

This time create a Visual Studio class project and add a reference to NUnit.Framework assembly. Modify the class1.cs to look like the below code.

using System;

using NUnit.Framework;

namespace KruyzKontrol{

    /// <summary>

    /// Summary description for Class1.

    /// </summary>


    public class Class1{

        public Class1(){


            // TODO: Add constructor logic here




        public void FailTest(){

            Assert.Fail("This test will fail and CC will show the message to me");




Save the project somewhere else (other than CCExample folder) with the name Test and send it to Subversion with TortoiseSVN under CCExample\Test.

We will have some modifications on the file to integrate with NUnit tests. We need to clean up the test folder if exist, download NUnit test project from Subversion, compile both test project and BestCode.cs and execute the tests. When we get everything up and running, we will handover the process to Cruise Control and sit back & relax. Below is the modified version of the file.

<?xml version="1.0"?>

<project name="CCExample" default="build" basedir=".">

<record name="Buildlog.txt" level="Info" action="Start"/>  

    <description>any description</description>

    <property name="debug" value="true" />

    <property name="defaultframework" value="net-1.1" />

    <target name="build" depends="get">

        <csc target="exe" output="BestCode.exe" debug="${debug}">


                <include name="BestCode.cs" />



        <solution configuration="debug" solutionfile="Test\CCTest.sln" />


            <formatter type="Xml" />

            <test assemblyname="Test\bin\debug\CCTest.dll" />



    <target name="get" depends="clean">

            <svn command="checkout"







  <target name="clean" >

            <delete dir="Test" failonerror="false" />

        <mkdir dir="Test" />

        <delete file="BestCode.exe" failonerror="false" />

        <delete file="BestCode.pdb" failonerror="false" />


   <record name="Buildlog.txt" action="Close"/>


<URI> is the Subversion folder where your test project resides.

<DESTINATION> is the working directory for the test project.

There are multiple targets in this one and they are dependant to each other. First the "clean" target will clean up the existing folders, "get" target will download the test project from Subversion, "build" target will compile the projects and execute the NUnit tests. Open a command prompt to the project folder and enter the below command.

D:\Workbench\CSharp\Deneme\>nant -t:net-1.1

If you are seeing an error message saying that build failed, then everything is okay. This is what we want. Now we may handover the process to Cruise Control. Run the ccnet.exe and browse to http://localhost/ccnet/default.aspx. Check the builds and see the error message that we have setted in the code.


Comments for this entry:

# re: Cruise Control and Subversion

this is 1 of the better How To setup CC.Net & SVN articles

by doesn't matter on  7/11/2006 6:23 AM
# re: Cruise Control and Subversion

Good article, I still think with subversion was harder to set up then it should have been. I ran into a bunch of gotchas.

by good article on  7/7/2007 4:52 AM
# re: Cruise Control and Subversion

where can i find something identical to this but working with ubuntu?

by Pablo on  8/31/2008 6:30 PM
# re: Cruise Control and Subversion

Thank you Gurkan, good article!

by realizzazione siti internet on  12/30/2008 2:45 AM
# re: Cruise Control and Subversion

That's great, I never thought about Cruise Control and Subversion like that before.

by Yachtcharter Griechenland on  1/31/2009 5:00 PM
# re: Cruise Control and Subversion

I find posts like this with supporting code really helpful. Thanks for the worked example.

by Birmingham banner stands experts on  3/22/2010 9:13 PM
# re: Cruise Control and Subversion

Thanks much, Gurkan.

Can any one please help me with this query on this article?

I see we are configuring the svn information TWICE in the ccnet.config file XML as displayed here. May I know why 2 times? or am I missing something here?


for my exact pointer detail.



by VC on  5/6/2011 7:56 AM
# re: Cruise Control and Subversion

This is really a good write up and appreciate your steps.

Just wondering if you could help answer this query I posted with ref. to this write up.



by VC on  5/6/2011 10:52 AM

Enter your comment here

Comments are moderated



 (not displayed)

 (will be a link on your name)

Bold Italic Underline Blockquote Hyperlink Hyperlink


Please add 7 and 3 and type the answer here:

Comment Preview:



About me

Hi, my name is Gurkan Yeniceri. I am a software engineer with 8 years of experience in both public and private sectors. I have been generally writing about software engineering and Microsoft technologies since March 2005 on this site.
View Gurkan Yeniceri's profile on LinkedIn


If you would like to contact with me you can use the contact page here. I will try to respond it in a timely manner (I will try my best). You can also contact with me via Microsoft Live Messenger with the address gyeniceri {AT} hotmail {DOT} com.
If you are one of my Turkish readers, you may want to visit my Turkish blog here.

If you would like to read my site with an RSS reader like RSS Bandit, you may want to use to subscribe.

RSS 2.0


Bookmark this site digg NewsVine YahooMyWeb Reddit Spurl TailRank BlinkList Furl Shadows blogmarks
    This is a Flickr badge showing public photos from gurkanyeniceri. Make your own badge here.
    There are 133 posts and 88 comments on this site. Other sites also linked it 7 times.