Multiple Source Control Configuration w/ CCNET

I just painted myself into a corner with our CruiseControl.NET server or so I thought. I wanted to monitor two source code repositories in our version control system (we use Seapine Surround SCM) and run a build script if code in either repository changes.

The first path I went down was to make two CruiseControl.NET projects each with their own <sourcecontrol> element to monitor the respective repositories. These trigger the same build script that builds a whole bunch of assemblies and does the normal stuff. There is a build concurrency problem when you have a check-in with files from each monitored repositories. With they way I’ve setup the build script the builds can start colliding and I got unpredictable results.

The solution? Turns out there’s a “multi” source control type that lets you specify more than one source control provider for a single project. Fantastic!

Read the details here.