Remove one-one binding between collection and build controller
a team build server can be used by a single TFS only.
It would be more convenient a team build server can be used by multiple Team Foundation Server.
In addition installing multiple build server build agent on same physical/virtual server would be convenient - it is possible to install multple agents on the same server but this requires manual configuration and patching the system.
Craig Gamble commented
This is one of the most annoying things about TFS2010 and i thought you may have removed it come tfs2012. why have the concept of using collections when the build controller can only service 1 collection.
we have multiple collections which house specific architecture projects, i just find it frustrating that any new collection requires a new build controller (read new server)
Francisco Jose Peredo commented
I believe is a limitation that shouldn't exist, one should define the build controllers based on the number of projects and their particular complexity, and not based on structure of the project collections
Jim Lamb commented
It would be really helpful to hear some specifics as to why you need a build controller to service multiple project collections. In most cases, I've found that teams are creating too many project collections which results in a variety of problems due to the resulting isolation. If you voted on this suggestion, I'd like to hear how many developers are using TFS in your organization, how many project collections, you have, how many build controllers you have and how many build machines (controllers and agents) you have altogether.
The same for us. Just we need to share one build server between multiple project collections.
There is a workaround, but this is not official solution. http://blogs.msdn.com/b/jimlamb/archive/2010/04/13/configuring-multiple-tfs-build-services-on-one-machine.aspx