Team Build 2005 did not support Continuous Integration out of the box. Lots of add-ins and tools have been released since Team Build released to do CI. Here's an admittedly incomplete list for doing Continuous Integration with Team Build:
- Automaton
- Notion Solutions Team CI
- TFS Integrator
- CI Sample and the Vertigo version
- TFSBuildLab, which I just covered
- TeamBuild plugin for CruiseControl.NET, also using the VSTS plugin for CC.NET
I've personally used CruiseControl.NET and the CI Sample in projects, and tested out several of the others. I'd probably stick with using CruiseControl.NET for now, as it has the easiest access to build status and reports with the dashboard and tray application. It's also been around for many years and many versions, so it's solid product that can provide some transition to Team Build if your team is already using CC.NET.
.png)
No comments:
Post a Comment