CruiseControl.Net problem - can't get latest source

ChrisHolmes · Post by **ChrisHolmes** » Fri Feb 02, 2007 3:33 pm

We're banging our head against this problem and can't find any documentation anywhere to let us know one way or the other if the problem we're experiencing is normal or not.

We're using CruiseControl.NET with Vault. From the command line the Vault client works great - it will fetch the latest source and with the -merge overwrite command we're guarenteed the latest files prior to invoking MSBuild.

But the moment we try and do the same thing with our CC.NET config file it doesn't work. The build runs just fine, and CC.NET reports to us the build is ok, but when we inspect an executable we discover that the latest version of the code was NOT pulled down (we're changing the background color on a form as an easy way to test if the build got the latest version or not).

Is this a common issue? Or are people able to actually get the latest version from Vault using CC.NET using some mystic power we're unaware of?

We're all really tired and beat trying to make this work.

Beth · Post by **Beth** » Fri Feb 02, 2007 4:45 pm

Are you using a set path that is different than the working folders? We've had one user at this post that had problems with -destpath.

Can you write out the command being used in CC.Net?

ian_sg · Post by **ian_sg** » Sat Feb 03, 2007 12:17 pm

Chris is getting help on the ccnet-user mailing list. I'll make sure the issue and resolution end up here, as well.

ian_sg · Post by **ian_sg** » Mon Feb 12, 2007 10:05 am

This ended up being a mistake in the CCNet config file. Specifically, the <sourcecontrol> element was inside the <tasks> element.