Apologies for being quiet on the blogging front lately, we’ve been busy getting ready for TechEd in Boston next week. I’ll soon be able to share some exciting news so stay tuned. One of the areas I have been playing with in my spare time recently is with CodePlex – the new developer community site from Microsoft that uses Team Foundation Server for Version Control and Work Item Tracking. I noticed that the Turtle project had a work item to configure CruiseControl.NET to talk to their project tree so I thought I’d quickly describe how to do it here in case anyone else is interested.
First things first, you’ll need to install CruiseControl.NET 1.0 on your build server, the TFS Client and also the TFS Source Control Block from VSTSPlugins. (To be honest, you don’t actually need to install the TFS Client, you could just copy the appropriate assemblies into the CruiseControl server directory).
Then, you have to configure the source control block (along with your tasks and publishers) in your ccnet.config file. Below is an example:-
<sourcecontrol type="vsts" autoGetSource="true" applyLabel="false">
<buildArgs>/noconsolelogger /p:Configuration=Debug /v:diag</buildArgs>
<!-- Insert publishers here -->
Remember to substitute “USERNAME” and “PASSWORD” for your appropriate values. Note that your username should be suffixed with _cp. In the example above, I’m using the MSBuild Task – more information on that is available here.
Anyway, it all seems to work perfectly. All this has reminded me that I want to fix / improve a few things with the CruiseControl.NET plugin – better add that to my todo list – but hopefully it should be good to get people started.
Update: As I’m currently sat in a Hotel room I figured I should just make those changes. They appeared to be easier than I thought and worked first time – but I’ve probably introduced a few new bugs. Anyway, feel free to download the latest version and let me know how you get on.