CruiseControl .NET
Essentially how CruiseControl .NET works is by periodically polls and detects for modifications on the source repository and upon detection of modifications, it kickstarts a NAnt build script (bootstrap build script), which run an update and checkout the necessary changes from the source repository. Next it attempt to perform a build on the project's working source code by calling the project's default NAnt build script.
CruiseControl .NET --> cruise.build (NAnt script) --> cvs checkout --> project.build (NAnt build script)
Quick rough guide to installing CruiseControl .NET
- Obtain the distribution and unzip it. Refer the unzipped folder as ccnet folder.
- Create a ccnet.config file under the server folder in ccnet folder.
- Configure ccnet.config with definitions for cvs client, cvsroot, bootstrap NAnt script that going to be called by ccnet and publishers.
- Create a bootstrap NAnt build script and call it cruise.build.
- In cruise.build, specify the project build file to be built.
- Start ccnet in the folder where your ccnet.config file is located.
Debugging tips
- Check your ccnet.config and make sure that the xml is valid and the detail settings are correct
- If ccnet start up fine but do not seems to be doing what it should be, check the log file for errors. There's two kind of log files being generated: ccnet.log logs the status of ccnet, while the xmllogger publisher defined in the ccnet.config, logs the actual actions and process by ccnet.
- If files are not updated, check your cvs settings and check the log file for errors.
- If the FxCop link on the build page does not work, make sure you have merge the fxcop result xml file with the build log.
- Getting a blank or page not found error, when click on original log link on the web build page? If the web app logDir is configured to an arbitrary folder, \myLogDir, make sure to create a virtual directory “log“ that points to it as well.