As you already know, CruiseControl.Net is an open source framework for build automation. Though there are hundreds of articles on the topic in the web, I was unable to find one that suited me as a starter. Hope this article helps people like me out there who want to get a taste of the continuous integration process using CruiseControl.Net, Visual Source Safe and Visual Studio.
I intend to showcase the bare minimum steps involved to automate the build process of an ASP.NET Visual Studio 2005 solution.
- Visual Studio 2005 IDE
- Visual SourceSafe
Install the setup files for CC.net either using the MSI installer or simply unzip the zip file (I used the later approach). You will find four folders namely, cctray, examples, server and webdashboard. Edit the ccnet.config file in the server to make it look like the following:
<project name="MyProjectBuild" queue="Q1" queuePriority="1">
<sourcecontrol type="vss" autoGetSource="true" applyLabel="true">
<executable>C:\Program Files\Microsoft Visual Studio\
<executable>C:\Program Files\Microsoft Visual Studio 8\
<xmllogger logDir="c:\TestCC\buildlogs" />
The above XML shows that I have my VSS db in another machine on the network \\filesvr1\myproj. I want CC.NET to get a clean copy of the source from vss location $/MyProject/Source to my local folder c:\testcc. Instruct VS IDE to build the solution c:\testcc\src\MySolution.sln.
Now I am ready to run the server. All I need to do is issue the following command from the command line:
This will immediately integrate the project
MyProjectBuild. The verbose output can be seen in the command prompt itself. To get a better view, the web dashboard needs to be configured. This can be done by simply creating a website pointing to the dashboard folder. Navigating to the default page would show the project integration status. Note that the ccnet.exe server has to be running to view the build status.
You can also apply triggers to schedule the build. This can be done quite easily using the
You can see how easy it is to get CruiseControl.Net running. This article just describes how to automate the build. The build is still not ready for deployment. Meaning I may want to place the build in another folder for release without the code behind. This is covered in the article, Automating ASP.NET Web Application project build using CruiseControl.Net and MSBuild.
This member has not yet provided a Biography. Assume it's interesting and varied, and probably something to do with programming.