The build controller can live on any machine, but it’s always a best practice to keep it on a separate machine than the TFS Server. If a new Team Project Collection is added to TFS, that collection, you would assign one or more controllers to it, but you cannot assign a controller to more than one collection. The way it works is that a build controller is assigned to a Team Project Collection. This illustration from MSDN describes the relationship between a Team Project Collection, a Build Controller, and a Build Agent: TFS 2010 introduced the concept of Build Controllers, which are responsible for managing one or more Build Agents in order to work through a build queue. Not much changed in the way that builds were executed through agents between TFS 20. Today we are going to take a look at Build Agents and Build Controller. A lot of its basic functionality, such as MSBuild integration, has not changed at all, but its moving pieces and configuration have changed drastically.

This being its third iterations (2005, 2008, and now 2010), it has grown a lot since it first came out. Having looked at a few different build systems in the past, I have yet to see one with as much power and flexibility as Team Build.

As you may already know, TFS includes a very powerful build system called Team Build.

Ultracopier follow strict order