Since TFS2010, because there’s been the introduction of project collections, build agents are quite the trouble for IT admins.
On one hand, there’s the fact that putting every project in a single collection can be a maintenance and project isolation nightmare, and on the other hand the fact that there can officially be one build controller per machine tied to a single project collection, forcing to have many machines to support continuous integration build environments.
Luckily, there’s been a workaround published two years ago on how to run multiple build services on the same machine, and it’s working pretty fine.
However with TFS2012, this hack needs to be adjusted to work properly.
Prior to running the configuration tool, instead of setting this:
The new environment variable is:
I’m guessing that this can be used to run both 2010 and 2012 build services on the same machine without interferences, though I haven’t tried it.
Just as a reminder, to use this feature, you need to set non-overlapping build working folders and different listening ports for every new instance. This will avoid conflicts…
Works pretty great, now with TFS2012 !