R – CruiseControl.NET: Building a project in Debug and Release configurations

build-automationcontinuous integrationcruisecontrol.net

I am using CruiseControl.NET to build a C# project. I am using an msbuild task to achieve this. I want to build the project in both Debug and Release mode irrespective of whether either mode fails. But If I put these as two msbuild tasks in the 'tasks' section of the project and if the first task fails, the second is not executed.

I could define them as two projects, but I want the Label to be synchronized across both the projects. Is there a way to do this?

One solution I have is make the 'Release' config project to trigger a build whenever the 'Debug' config project is built. But in that case, If someone force builds the 'Debug' config project then, the labels will get out of sync.

Best Answer

To achieve what you want, I think you will have to use a custom task to call MSBUILD from a CMD file and pass the debug/release mode into MSBUILD via cmd line args.

Related Solutions

CruiseControl.net, msbuild, /p:OutputPath and CCNetArtifactDirectory

The CCNetArtifactDirectory is passed to the MSBuild by default, so you dont need to worry about it. MSBuild will place the build output in the "bin location" relevant to the working directory that you have specified.

<executable>c:\WINDOWS\Microsoft.NET\Framework\v3.5\MSBuild.exe</executable>
<workingDirectory>C:\data\projects\FooSolution\</workingDirectory>
<projectFile>FooSolution.sln</projectFile>
<buildArgs>/noconsolelogger /p:Configuration=Debug </buildArgs>

So in the above example your build output will be put in C:\data\projects\FooSolution[ProjectName]\bin\Debug. Should you want to output to a different location you may want to look at of the tag in CCNET.

<publishers>
  <xmllogger />
  <buildpublisher>
    <sourceDir>C:\data\projects\FooSolution\FooProject\bin\Debug</sourceDir>
    <publishDir>C:\published\FooSolution\</publishDir>
    <useLabelSubDirectory>false</useLabelSubDirectory>
  </buildpublisher>
</publishers>

This will allow you to publish your output to a different location.

R – cruisecontrol sourcesafe block

In the end we have switched from SourceSafe to SourceGear Vault (mainly for branching features, but speed and reliability were also large factors).

We have also moved our build machine from an old pc to a server which has a 1Gb/s connection to the source server, rather than 100Mb/s, which has helped considerably.

In the end when I was installing and testing Vault on the same machine (well, a clone) as the old build machine, it was cutting the source get operation from around 10 mins to 5. Once it was installed on the build server source get time is now around 1min.

My advice to anyone is just to switch from SourceSafe to anything else...you wont regret it.

Best Answer

Related Solutions

CruiseControl.net, msbuild, /p:OutputPath and CCNetArtifactDirectory

R – cruisecontrol sourcesafe block

Related Topic