Using CruiseControl.NET to trigger TFS 2005 builds for continuous integration
I ran across the following post by James Dawson and thought it may be of interest to folks trying to do CI with TFS 2005. Of course, you’ll find CI as part of the product in TFS 2008.
I’ve been meaning to write this post for a couple of months now as a follow-up to a session that Colin and I gave at the Microsoft Architect Insight Conference back in March, but just haven’t found the time… at least, that’s my excuse – anyway cutting to the chase!
Since the release of Team Foundation Server (TFS) there have been several Continuous Integration add-ons produced by various folks:
- CI Sample – (also its ‘Vertigo remix’)
- … and I dare say many more (not to mention the one that Microsoft are slated to ship with the Orcas release of VSTS)
We’ve used most of the above, but despite however well they worked have found myself wanting some feature or other that was available in CCNet (actually it more about being badgered by developers about the missing features!). Whilst some of the above could have been extended to support these features, I couldn’t help but feel that this would have been reinventing the wheel – hence the idea to extend CCNet.