Continuous Integration using CruiseControl.NET, NANT, CVS, and NUnit

• Download source files - 16 Kb

Introduction

Recently I set up a build system for a software development team working in .NET. I was interested in the Continuous Integration approach, where builds occur automatically as changes are detected in source control. My other goals were to keep my team's build process simple and understandable, and to group tasks in a way that makes sense and encourages reuse.

Most of my information was gained by reading of other developers' experiences documented on the web, but I could not find a single, comprehensive "newbie guide" on how to set up an entire system. My intention is to provide such an article, explain the logic behind my decisions, and perhaps ease the process for others implementing similar systems.

This article assumes that you have requisite tools already set up. I used VisualStudio 2005, CruiseControl.NET 1.0.1, NAnt 0.85-rc3, and NUnit 2.2.7. Tortoise CVS 1.8.26 is used as a CVS client, and IIS is needed for CruiseControl.NET's Web Dashboard.

Background

The developer's toolset is usually composed of at least the following tools:

• Source control repository to store code in a common location, and allow multiple developers to share a code base (e.g. CVS, Subversion, VSS).
• Unit testing framework to run unit tests which are written as part of the code development process, and can flag unintentional changes to code (e.g. NUnit, JUnit).
• Automated build tool to allow building from the command line, and to perform related tasks (e.g. Ant, NAnt, MSBuild).
• Continuous Integration tool which monitors for code changes and triggers builds (e.g. CruiseControl, Draco).

Build tools have increased in complexity over the years, and many overlap in functionality. As a result, implementation decisions can be endless. For example, should unit tests be run directly from CruiseControl, NAnt or MSBuild? If email notification is used, how should this be wired up? The answers lie in the strengths and weaknesses of each tool, but implementing or investigating each one can be time-consuming.

Flow Control

To aid in understanding of how this system works and what each component does, I've provided a typical scenario:

1. Developer commits code changes/additions to CVS.
2. CruiseControl.NET detects changes.
3. CruiseControl.NET updates code on build machine.
4. CruiseControl.NET invokes NAnt script.
5. NAnt script builds application using devenv.com
6. NAnt script runs unit tests Final CruiseControl.NET tasks support display of unit testing information.
7. CruiseControl.NET manages output files for display in its Web Dashboard.
8. CruiseControl.NET sends emails as appropriate.

Continuous Integration tool: CruiseControl.NET

Of the two most common open source Continuous Integration tools I chose CruiseControl.NET. I did not spend a lot of time comparing them, and my decision was based on the fact that some developers consider it more flexible. Its most useful features are its ability to poll source control for changes, and a powerful Web Dashboard (requires IIS) that provides a history of all builds and their details.

Initial Setup

The heavy lifting will involve setting up a project block in the ccnet.config file. Aside from that, you will probably want to turn on logging in the ccnet.exe.config file.

Automated build tool: NAnt

I found that running unit tests and builds in NAnt (invoked by CruiseControl) is more manageable than running them directly from CruiseControl. Packaging build and unit tests into a single NAnt script also allows for easier script debugging, and gives developers a tool which can build and test from the command line if desired. Because the default.build file is checked into CVS with the rest of the project, changing it will cause CruiseControl.NET to rebuild.

Both NAnt and CruiseControl.NET can run any executable and have tags dedicated to running unit tests. But NAnt provides more support for ancillary tasks such as file management, and its flow control is more flexible.

Initial Setup

Set up a default.build NAnt file in the base directory of the project, which builds the project and runs NUnit tests. For the tests, I recommend the Thea Burger's pattern that allows unit tests from multiple assemblies all to run to completion, despite a possible failure in one assembly.

<target name="test" description="runs the unit tests" >
    <!-- test first Assembly. -->
    <exec program="nunit-console.exe" failonerror="false" resultproperty="testresult.Main.exe">
        <arg value="RelativePath/Main.exe" />
        <arg value="/xml=UnitTest-Main.xml" />
    </exec>

    <!-- test second Assembly. -->
    <exec program="nunit-console.exe" failonerror="false" resultproperty="testresult.SecondaryAssembly.dll">
        <arg value="RelativePath/SecondaryAssembly.dll" />
        <arg value="/xml=UnitTest-SecondaryAssembly.xml" />
    </exec>

    <!-- Check the results properties and fail if necessary -->
    <fail message="Failures reported in unit tests." unless="${int::parse(testresult.Main.exe)==0}" />
    <fail message="Failures reported in unit tests." unless="${int::parse(testresult.SecondaryAssembly.dll)==0}" />
</target>

Compiler: MSBuild.exe or Devenv.com

These are the two options for building a .NET solution or project from NAnt or at the command line. I experimented with both, but used devenv.com because the current version of MSBuild cannot build setup files! MSBuild offers additional capabilities which overlap with the Ant/NAnt family, and some developers prefer it to devenv because it does not necessitate installation of Visual Studio on the build machine. However the setup shortcoming was a deal breaker, and there was no need to use both MSBuild and NAnt in the process.

It's worth noting that some tools belong in the solution, in post-build events. An example of this is obfuscation, which occurs only as part of the Release build and needs to be run before constructing the setup files.

Other tools: CVS and NUnit

For my project, the choices of CVS and NUnit were predetermined. CruiseControl provides similar tools for monitoring a variety of other code repositories as well. NUnit is prevalent, and has been used by my team on a number of projects.

More CruiseControl.NET Setup Pointers

The Merge Tag

Depending on how you wire up CruiseControl.NET, it might be necessary to "Merge" output from an invoked application, in order to get test results to appear in the Web Dashboard and in email messages. This is the case when invoking NUnit from NAnt as outlined above. When NAnt invokes when NUnit, xml output is explicitly requested.

<exec program="nunit-console.exe" failonerror="false" resultproperty="testresult.Main.exe">
    <arg value="RelativePath/Main.exe" />
    <arg value="/xml=UnitTest-Main.xml" /> <!-- keep xml output -->
</exec>

These files are then "merged" in ccnet.config.

<merge>
    <files>        
        <!-- these file names need to conform to those found in default.build -->
        <file>C:\cruisecontrol-dev\test\RegexDemo\UnitTest*.xml</file>
    </files>
</merge>

CruiseControl.NET recognizes the xml from NUnit (and a number of other apps as well) and knows what to do with it.

The Web Dashboard

Once all processes are running and visible, you can tweak the CruiseControl.NET Web Dashboard by changing dashboard.config or the xml, xsl and css that shape its content. The Email messages sent out by CruiseControl.NET are also controled in the same way, by a separate set of files.

Summary

In the final analysis, the build process outlined here is configured in three places: CruiseControl.NET's ccnet.config, the NAnt default.build, and in the solution itself. CruiseControl is a great system, and we've found unexpected uses for it even in the first few weeks. I continue to be impressed with its flexibility.

Sample code

The sample code contains an example of ccnet.config which builds a simple application with one unit test and no unusual dependencies. The sample app can be checked into cvs and used for testing. The default.build file is included as well.

You must Sign In to use this message board.

FAQ    Noise Tolerance Very HighHighMediumLowVery Low   Layout Expand Posts & RepliesThread ViewNo JavascriptNo JS + Preview   Per page 102550

Msgs 1 to 8 of 8 (Total in Forum: 8) (Refresh) FirstPrevNext

Working Directory In Remote System! s_90 23:03 22 Oct '08   hi i am using devenv.exe to build project.actually requirement s to have ccnet in one machine but working directory should be created in other machine.s it possible Sign In·View Thread·PermaLink about ci flyingchen 5:20 1 Nov '07   Your article is good . But now I want to know that have you really used the cc.net in your projects and how do you build your servers ? We know we need daily-build that can help us to get a new version everyday.so how do you get the new version and sent it to your file server ? thanks a lot！ Sign In·View Thread·PermaLink 5.00/5 (1 vote) I would like to store the sucessful build in a different folder with version or label. kuncha 2:13 18 Oct '07   Hi, Your article is very useful. I would like to give the successful exe to the client with version or label. How can I achieve this by using CCnet. Thanks. vedd Sign In·View Thread·PermaLink 2.00/5 (1 vote) Re: I would like to store the sucessful build in a different folder with version or label. Alex Rovner 5:35 28 Jul '08   Two approaches: 1. If you are using a version control system you can extract the latest revision checked out by CruiseControl and pass it down as an argument to the NAnt. 2. Generate the label your self based on date time stamp for example create the folder by supplying output directory for either msbuild or solution tasks. I know it's a bit general but hope this will help. Sign In·View Thread·PermaLink Good, but needs more to be truely helpful. [modified] poodull76 5:09 4 Oct '06   There are some things you haven't addressed in your article. Nant, nor MSBuild, does not build installation projects. DevEnv.exe can build installation projects. Nant does not build .Net 2.0 without the latest beta. Devenv will fail if you ever get a popup message while trying to compile using Nant. NUnit doesn't do .Net 2.0 with generics. What about setting up the CCNet Web Dashboard? CCNet Task Tray? Links on where to find the CCNet/Nant/etc downloads. Please don't take this the wrong way. I am only sugguesting that there should be much more to this article to make it more useful than the standard documentation that comes with these individual products. Below is my Nant and ccnet config. I hope it helps... You'll see I use CCNet to monitor VSS as well as kick of nightly builds. CCNet performs the 'get', then calls nant in either change or nightly mode. Change is just the 'clean, build, test' targets. Nightly is 'clean, build, test, mangle, install'. All compilation is at the solution level using MSBuild. The solution has many configurations other than Debug and Release. 'Test' is all the test projects, 'Dotfuscate' is our obfuscator, 'Installers' is just the installation projects. Builds are performed, then dlls are obfuscated, moved back to their original destination, then the installers configuration is called to pack them up. The nDoc task works, but it takes forever and is useless to us right now. So it is disabled. The key thing here is that all developers can use this default.build without any changes -- as well as CCNet -- thanks to the 'config' target at the top. Command line arguments can override most parameters. ... wish I had time to write this up better. Sign In·View Thread·PermaLink 2.80/5 (5 votes) default.build poodull76 5:10 4 Oct '06   <?xml version="1.0"?> <project name="Solution" default="rebuild">      <!--      *** The config target sets up any property variables needed for this, or      sub targets.   Put any global properties here.   Specific variables, like      Environment variables should go in the target they are need in only.      Subtargets needed these variables can link to them with the depends=      parameter.***      -->      <target name="config">           <!-- The FrameworkDir is the directory where the MSBuild and .Net framework exists -->           <property name="FrameworkDir" value="C:\windows\Microsoft.net\framework\v2.0.50727" unless="${property::exists('FrameworkDir')}"/>           <echo message="FrameworkDir = '${FrameworkDir}'"/>           <!-- The IDEDir is the directory where the VS IDE devenv.exe exists -->           <property name="IDEDir" value="C:\Program Files\Microsoft Visual Studio 8\Common7\IDE" unless="${property::exists('IDEDir')}"/>           <echo message="IDEDir = '${IDEDir}'"/>           <!-- The nDocDir is the directory where nDocConsole.exe exists -->           <property name="nDoc.bin" value="C:\software\nDoc\bin" unless="${property::exists('nDoc.bin')}"/>           <echo message="nDoc.bin = '${nDoc.bin}'"/>           <!-- The Configuration property tells the compiler what version to build -->           <property name="Configuration" value="Debug" unless="${property::exists('Configuration')}"/>           <echo message="Configuration = '${Configuration}'"/>           <!-- The ArtifactDir holds the build logs and output files.   not binaries. -->           <property name="ArtifactDir" value="${directory::get-current-directory()}\Artifact" unless="${property::exists('ArtifactDir')}"/>           <echo message="ArtifactDir = '${ArtifactDir}'"/>           <mkdir dir="${ArtifactDir}" failonerror="false"/>           <delete >                <fileset basedir="${ArtifactDir}">                     <include name="**/*"/>                </fileset>           </delete>           <!-- The CCNet property is used to assign some non-commandline settings when           CCNet is used to drive this NAnt file. -->           <if test="${property::exists('CCNet')}">                <echo message="*** CCNET Override Property found! ***"/>                <property name="MSBuildLogger"                value="ThoughtWorks.CruiseControl.MsBuild.XmlLogger,C:\Program Files\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MSBuild.dll"                     unless="${property::exists('MSBuildLogger')}"/>           </if>           <ifnot test="${property::exists('CCNet')}">                <property name="MSBuildLogger"                value="ConsoleLogger,${FrameworkDir}\Microsoft.Build.Engine.dll"                     unless="${property::exists('MSBuildLogger')}"/>           </ifnot>           <echo message="MSBuildLogger = '${MSBuildLogger}'"/>           <!-- The nDoc.Output is the directory where nDoc output will be placed -->           <property name="nDoc.Output" value="${directory::get-current-directory()}\Doc" unless="${property::exists('nDoc.Output')}"/>           <echo message="nDoc.Output = '${nDoc.Output}'"/>           <!-- The nDoc.Build is the directory where nDoc temporary build files will be placed -->           <property name="nDoc.Build" value="${directory::get-current-directory()}\Doc\Build" unless="${property::exists('nDoc.Build')}"/>           <echo message="nDoc.Build = '${nDoc.Build}'"/>           <mkdir dir="${nDoc.Build}" failonerror="false"/>           <delete >                <fileset basedir="${nDoc.Build}">                     <include name="**/*"/>                </fileset>           </delete>           <!-- The install.Output is the directory where Install target output will be placed -->           <property name="install.Output" value="${directory::get-current-directory()}\Deploy" unless="${property::exists('install.Output')}"/>           <echo message="install.Output = '${install.Output}'"/>           <delete >                <fileset basedir="${install.Output}">                     <include name="**/*"/>                </fileset>           </delete>      </target>      <!--      *** The 'get' target gets the latest version from sourcesafe ***      -->      <target name="get">           <!--Sets the local environment variable SSDir-->           <setenv name="ssdir" value="\\pigeon\VSS\APXX\"/>           <exec program="C:\Program Files\Microsoft Visual SourceSafe\SS.EXE" useruntimeengine="true">                <!--<arg value="get '$/Spiral 4' -R -YCCNET,CCNET -I-N -W- -GF- -GTM -GWR" />-->                <arg value="get" />                <arg value="$/Spiral 4" />                <arg value="-R" />                <arg value="-YCCNET,CCNET" />                <arg value="-I-N" />                <arg value="-W" />                <arg value="-GF-" />                <arg value="-GTM" />                <arg value="-GWR" />           </exec>      </target>      <target name="clean" depends="config">           <exec program="${FrameworkDir}\MSBuild.exe" useruntimeengine="true"                output="${ArtifactDir}\msbuild-${target::get-current-target()}-results.xml">                <arg value="Implementation.sln"/>                <arg value="/target:Clean" />                <arg value="/noconsolelogger" if="${property::exists('CCNet')}" />                <arg value="/nologo" if="${property::exists('CCNet')}" />                <arg value="/p:Configuration=${Configuration}" />                <arg value="/verbosity:normal" />                <arg value="/logger:${MSBuildLogger}" unless="${MSBuildLogger==''}"/>           </exec>      </target>      <target name="build" depends="config">           <exec program="${FrameworkDir}\MSBuild.exe" useruntimeengine="true"                output="${ArtifactDir}\msbuild-${target::get-current-target()}-results.xml">                <arg value="Implementation.sln"/>                <arg value="/target:Build" />                <arg value="/noconsolelogger" if="${property::exists('CCNet')}" />                <arg value="/nologo" if="${property::exists('CCNet')}" />                <arg value="/p:Configuration=${Configuration}" />                <arg value="/verbosity:normal" />                <arg value="/logger:${MSBuildLogger}" unless="${MSBuildLogger==''}"/>           </exec>      </target>      <target name="test" depends="config">           <exec program="${FrameworkDir}\MSBuild.exe" useruntimeengine="true"                output="${ArtifactDir}\msbuild-${target::get-current-target()}-results.xml">                <arg value="Implementation.sln"/>                <arg value="/target:Rebuild" />                <arg value="/noconsolelogger" if="${property::exists('CCNet')}" />                <arg value="/nologo" if="${property::exists('CCNet')}" />                <arg value="/p:Configuration=Test" />                <arg value="/verbosity:normal" />                <arg value="/logger:${MSBuildLogger}" unless="${MSBuildLogger==''}"/>           </exec>                     <nant target="${target::get-current-target()}">                <buildfiles>                     <include name="**/*.build" />                     <exclude name="default.build" />                </buildfiles>           </nant>      </target>      <!-- There is no good way to build MSI files from NAnt yet.   WIX is too      complex.   A hack is to open the IDE and have it build the 'Installers'      configuration-->      <target name="install" depends="config">           <!-- Installer Configuration builds all installers.   Have to manually           add this configuration setting because command-line arguements cannot be           overwritten.   ie, setting D:Configuration=Release would cause this to build           the Release config, despite any re-assignments in this script. -->           <echo message="Configuration = 'Installers'"/>           <exec program="${IDEDir}\devenv.exe" >                <arg value="Implementation.sln"/>                <arg value="/build" />                <arg value="Installers" />                <arg value="/out" />                <arg value="${ArtifactDir}\installer.build.txt" />           </exec>           <copy todir="${install.Output}" flatten="true">                <fileset>                     <include name="**/Release/*.msi" />                </fileset>           </copy>      </target>      <target name="doc" depends="config">           <copy todir="${nDoc.Build}" flatten="true">                <fileset>                     <include name="**/*.xml" />                     <include name="**/*.dll" />                     <include name="**/*.exe" />                </fileset>           </copy>           <!-- Calling the .nDoc xml file does not work with nDoc 1.3.1851.0           <exec program="${nDoc.bin}\nDocConsole.exe" useruntimeengine="true" >                <arg value="-project=APEX.ndoc" />                <arg value="-verbose" />           </exec>-->           <exec program="${nDoc.bin}\nDocConsole.exe" useruntimeengine="true" >                <!-- Projects -->                <arg value="${nDoc.Build}\Agent.HM.HMClient.Module.dll,${nDoc.Build}\Agent.HM.HMClient.Module.xml" />                <arg value="${nDoc.Build}\Agent.HM.HMClient.Shell.exe,${nDoc.Build}\Agent.HM.HMClient.Shell.xml" />                <arg value="${nDoc.Build}\Agent.HM.HMConsole.exe,${nDoc.Build}\Agent.HM.HMConsole.xml" />                <arg value="${nDoc.Build}\Agent.HM.HMEngine.dll,${nDoc.Build}\Agent.HM.HMEngine.xml" />                <arg value="${nDoc.Build}\Agent.HM.HMLibrary.dll,${nDoc.Build}\Agent.HM.HMLibrary.xml" />                <arg value="${nDoc.Build}\Agent.HM.HMService.exe,${nDoc.Build}\Agent.HM.HMService.xml" />                <arg value="${nDoc.Build}\Analysis.dll,${nDoc.Build}\Analysis.xml" />                <arg value="${nDoc.Build}\Agent.HM.HMClient.Common.dll,${nDoc.Build}\Agent.HM.HMClient.Common.xml" />                <arg value="${nDoc.Build}\Vecmath.dll,${nDoc.Build}\Vecmath.xml" />                <arg value="${nDoc.Build}\Utility.dll,${nDoc.Build}\Utility.xml" />                <arg value="${nDoc.Build}\TDService.exe,${nDoc.Build}\TDService.xml" />                <arg value="${nDoc.Build}\TDServerLibrary.dll,${nDoc.Build}\TDServerLibrary.xml" />                <arg value="${nDoc.Build}\TDServer.exe,${nDoc.Build}\TDServer.xml" />                <arg value="${nDoc.Build}\TDMessages.dll,${nDoc.Build}\TDMessages.xml" />                <arg value="${nDoc.Build}\TDLibrary.dll,${nDoc.Build}\TDLibrary.xml" />                <arg value="${nDoc.Build}\TDConsole.exe,${nDoc.Build}\TDConsole.xml" />                <arg value="${nDoc.Build}\SocketClientLibrary.dll,${nDoc.Build}\SocketClientLibrary.xml" />                <arg value="${nDoc.Build}\ScanEngineLib.dll,${nDoc.Build}\ScanEngineLib.xml" />                <arg value="${nDoc.Build}\Scan Engine GUI.exe,${nDoc.Build}\Scan Engine GUI.xml" />                <arg value="${nDoc.Build}\RMService.exe,${nDoc.Build}\RMService.xml" if="${file::exists('${nDoc.Build}\RMService.xml')}" />                <arg value="${nDoc.Build}\RMServerLibrary.dll,${nDoc.Build}\RMServerLibrary.xml" />                <arg value="${nDoc.Build}\RMServer.exe,${nDoc.Build}\RMServer.xml" />                <arg value="${nDoc.Build}\RMMessages.dll,${nDoc.Build}\RMMessages.xml" />                <arg value="${nDoc.Build}\RMLibrary.dll,${nDoc.Build}\RMLibrary.xml" />                <arg value="${nDoc.Build}\RMConsole.exe,${nDoc.Build}\RMConsole.xml" />                <arg value="${nDoc.Build}\RMClientLibrary.dll,${nDoc.Build}\RMClientLibrary.xml" />                <arg value="${nDoc.Build}\Resources.dll,${nDoc.Build}\Resources.xml" />                <arg value="${nDoc.Build}\MssClient.dll,${nDoc.Build}\MssClient.xml" />                <arg value="${nDoc.Build}\EnergyHistoryInterface.exe,${nDoc.Build}\EnergyHistoryInterface.xml" />                <arg value="${nDoc.Build}\DevicesLibrary.dll,${nDoc.Build}\DevicesLibrary.xml" />                <arg value="${nDoc.Build}\DataLibrary.dll,${nDoc.Build}\DataLibrary.xml" />                <arg value="${nDoc.Build}\Controls.dll,${nDoc.Build}\Controls.xml" />                <arg value="${nDoc.Build}\CalibrationLibrary.dll,${nDoc.Build}\CalibrationLibrary.xml" />                <arg value="${nDoc.Build}\Calibration.exe,${nDoc.Build}\Calibration.xml" />                <arg value="${nDoc.Build}\Blackbird.dll,${nDoc.Build}\Blackbird.xml" />                <arg value="${nDoc.Build}\BetaModules.dll,${nDoc.Build}\BetaModules.xml" />                <arg value="${nDoc.Build}\AnalysisModules.dll,${nDoc.Build}\AnalysisModules.xml" />                <!-- Documentor -->                <arg value="-documenter=MSDN" />                <arg value="-OutputDirectory=${nDoc.Output}\MSDN" />                <arg value="-Title='APEX Documented Class Library'" />                <arg value="-BinaryTOC=True" />                <arg value="-CopyrightText=Copyright (c) Agent Technologies 2003-2006&#xD;&#xA;&#xD;&#xA;All Rights Reserved.   Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the   copyright laws.&#xD;&#xA;&#xD;&#xA;Agent Technologies, Inc.&#xD;&#xA;395 Page Mill Road, Palo Alto, CA 94303-0870, U.S.A.&#xD;&#xA;" />                <arg value="-CleanIntermediates=True" />                <!-- Linear_Html creates one large html file.                <arg value="-documenter=Linear_Html" />-->                <!-- JavaDoc not working in nDoc 1.3.1851.0                <arg value="-documenter=JavaDoc" />-->           </exec>           <delete>                <fileset>                     <include name="${nDoc.Build}\*.*"/>                </fileset>           </delete>      </target>      <target name="mangle" depends="config">           <delete >                <fileset basedir="Dotfuscator/${Configuration}/Dotfuscated">                     <include name="**/*"/>                </fileset>           </delete>           <exec program="${FrameworkDir}\MSBuild.exe" useruntimeengine="true"                output="${ArtifactDir}\msbuild-${target::get-current-target()}-results.xml">                <arg value="Implementation.sln"/>                <arg value="/target:Rebuild" />                <arg value="/noconsolelogger" if="${property::exists('CCNet')}" />                <arg value="/nologo" if="${property::exists('CCNet')}" />                <arg value="/p:Configuration=Dotfuscator" />                <arg value="/verbosity:normal" />                <arg value="/logger:${MSBuildLogger}" unless="${MSBuildLogger==''}"/>           </exec>           <call target="replaceDlls"/>      </target>      <!-- Replaces dlls from the Dotfuscated folder to any instance of them elsewhere.           This is the only way I could get our install packages working without re-           writing the whole thing.      -->      <target name="replaceDlls">           <foreach item="File" property="source">                <in>                     <items>                          <include name="Dotfuscator/${Configuration}/Dotfuscated/**" />                     </items>                </in>                <do>                     <echo message="looking for: ${path::get-file-name(source)}." />                     <foreach item="File" property="destination">                          <in>                               <items>                                    <include name="**/${Configuration}/${path::get-file-name(source)}" />                                    <exclude name="Dotfuscator/**" />                               </items>                          </in>                          <do>                               <echo message="found copy in ${destination}." />                               <copy file="${source}" tofile="${destination}" overwrite="true"/>                          </do>                     </foreach>                </do>           </foreach>      </target>      <target name="rebuild" depends="clean,build"/>      <target name="all" depends="clean,build,test,doc,install"/>      <target name="*">           <echo message="Target '${project::get-name()}.${target::get-current-target()}' not implemented."/>      </target> </project> Sign In·View Thread·PermaLink 2.00/5 (1 vote) ccnet.config poodull76 5:18 4 Oct '06   <cruisecontrol>      <!-- This is your CruiseControl.NET Server Configuration file. Add your projects below! -->      <project>           <name>Apex_Spiral4</name>           <webURL>http://pigeon/ccnet/default.aspx?_action_ViewProjectReport=true&amp;server=local&amp;project=Apex_Spiral4</webURL>           <workingDirectory>C:\Source\CCNet\Apex\Spiral4</workingDirectory>           <artifactDirectory>Artifacts</artifactDirectory>           <modificationDelaySeconds>10</modificationDelaySeconds>           <publishExceptions>true</publishExceptions>           <sourcecontrol type="vss" autoGetSource="true"><!--applyLabel="true"-->                <executable>C:\Program Files\Microsoft Visual SourceSafe\SS.EXE</executable>                <applyLabel>false</applyLabel>                <project>$/Spiral 4</project>                <username>CCNET</username>                <password>CCNET</password>                <ssdir>\\pigeon\VSS\APXX\</ssdir>                <workingDirectory>C:\Source\CCNet\Apex\Spiral4</workingDirectory>                <cleanCopy>true</cleanCopy>           </sourcecontrol>           <triggers>                <intervalTrigger seconds="600" buildCondition="IfModificationExists"/>           </triggers>           <tasks>                <!-- *** Nant 0.85_rc3 does not support .Net 2.0 *** -->                <nant>                     <executable>C:\software\Nant\bin\NAnt.exe</executable>                     <baseDirectory>.</baseDirectory>                     <buildArgs>-D:CCNet=True -D:Configuration=Release</buildArgs>                     <nologo>false</nologo>                     <buildFile>default.build</buildFile>                     <logger>NAnt.Core.XmlLogger</logger>                     <targetList>                          <target>clean build test</target>                     </targetList>                     <buildTimeoutSeconds>1400</buildTimeoutSeconds>                </nant>                <!-- *** MSBuild is being called from Nant *** -->                <!--<msbuild>                     <executable>C:\windows\Microsoft.net\framework\v2.0.50727\MSBuild.exe</executable>                     <workingDirectory>.</workingDirectory>                     <projectFile>Implementation.sln</projectFile>                     <buildArgs>/noconsolelogger /p:Configuration=Release /verbosity:normal</buildArgs>                     <targets>Clean;Build</targets>                     <timeout>180</timeout>                     <logger>ThoughtWorks.CruiseControl.MsBuild.XmlLogger,C:\Program Files\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MSBuild.dll</logger>                </msbuild>-->           </tasks>           <publishers>                <merge>                     <files>                          <file>.\Artifacts\*-results.xml</file>                          <file>.\fxcop\*.xml</file>                          <file>.\Coverage.xml</file>                     </files>                </merge>                <xmllogger logDir=".\buildlogs" />           </publishers>           <externalLinks>                <externalLink name="IssueManager" url="http://pigeon/issuemanager/" />                <externalLink name="IIS Root Web on Pigeon" url="http://pigeon/" />           </externalLinks>      </project>           <project>           <name>Apex_Spiral4.Nightly</name>           <webURL>http://pigeon/ccnet/default.aspx?_action_ViewProjectReport=true&amp;server=local&amp;project=Apex_Spiral4.Nightly</webURL>           <workingDirectory>C:\Source\CCNet\Apex\Spiral4</workingDirectory>           <artifactDirectory>Artifacts.Nightly</artifactDirectory>           <modificationDelaySeconds>10</modificationDelaySeconds>           <publishExceptions>true</publishExceptions>           <sourcecontrol type="vss" autoGetSource="true">                <!--applyLabel="true"-->                <executable>C:\Program Files\Microsoft Visual SourceSafe\SS.EXE</executable>                <applyLabel>false</applyLabel>                <project>$/Spiral 4</project>                <username>CCNET</username>                <password>CCNET</password>                <ssdir>\\pigeon\VSS\APXX\</ssdir>                <workingDirectory>C:\Source\CCNet\Apex\Spiral4</workingDirectory>                <cleanCopy>true</cleanCopy>           </sourcecontrol>           <triggers>                <scheduleTrigger time="23:30" buildCondition="ForceBuild" />           </triggers>           <tasks>                <!-- *** Nant 0.85_rc3 does not support .Net 2.0 *** -->                <nant>                     <executable>C:\software\Nant\bin\NAnt.exe</executable>                     <baseDirectory>.</baseDirectory>                     <buildArgs>-D:CCNet=True -D:Configuration=Release -D:nDocOutput=C:\Inetpub\wwwroot\APEX_Spiral4</buildArgs>                     <nologo>false</nologo>                     <buildFile>default.build</buildFile>                     <logger>NAnt.Core.XmlLogger</logger>                     <targetList>                          <target>clean build mangle install</target>                     </targetList>                     <buildTimeoutSeconds>3000</buildTimeoutSeconds>                </nant>                <!-- *** MSBuild is being called from Nant *** -->                <!--<msbuild>                     <executable>C:\windows\Microsoft.net\framework\v2.0.50727\MSBuild.exe</executable>                     <workingDirectory>.</workingDirectory>                     <projectFile>Implementation.sln</projectFile>                     <buildArgs>/noconsolelogger /p:Configuration=Release /verbosity:normal</buildArgs>                     <targets>Clean;Build</targets>                     <timeout>180</timeout>                     <logger>ThoughtWorks.CruiseControl.MsBuild.XmlLogger,C:\Program Files\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MSBuild.dll</logger>                </msbuild>-->           </tasks>           <publishers>                <merge>                     <files>                          <file>.\Artifacts\*-results.xml</file>                          <file>.\fxcop\*.xml</file>                          <file>.\Coverage.xml</file>                     </files>                </merge>                <xmllogger logDir=".\buildlogs\Nightly" />           </publishers>           <externalLinks>                <externalLink name="IssueManager" url="http://pigeon/issuemanager/" />                <externalLink name="IIS Root Web on Pigeon" url="http://pigeon/" />           </externalLinks>      </project> </cruisecontrol> -- modified at 10:32 Wednesday 4th October, 2006 Sign In·View Thread·PermaLink 1.67/5 (3 votes) Re: Good, but needs more to be truely helpful. Michael Mendelson 20:45 5 Oct '06   Hey Poodull, thanks for your comments. I believe I mentioned a couple of your suggested issues (MSBuild issues, Web console), but did not cover them in detail. Perhaps I will go back and add more detail at some point. But I purposefully did not "deep dive" into CC.Net or the other products. I was mostly interested in the "contact points" between the products and the features that affected my decisions of how to use them. Also, thanks for posting your configuration! This is just the sort of thing I was looking for when setting up my system. I invite more people to post configurations here, or better yet, selections with explanations of why things were done this way. Sign In·View Thread·PermaLink 2.45/5 (6 votes)

Last Visit: 13:43 6 Jul '09     Last Update: 13:43 6 Jul '09 1