Need support for multiple TFS connections from a single server

Dec 8, 2011 at 1:56 PM

I'm uisng TFS Deployerto allow development to release core assets to our NuGet local package source.  These development assets are being developed using different TFS collections from different server.  When you run TFS deployer you have to pint it to a single collection.  How can I support TFS deployer on a single server going to multiple TFS collections? I thought of trying to run several instances each one pointing to different collections, but you have to run the command Listen on the configured HTTP endpoint.

     netsh http add urlacl url=http://+:8881/ user=YourDomain\YourTfsDeployerAccount


I assume that TFS broadcast to listeners on this port so if I ran multiple instances I would have to change some setting in TFS and I do not know what the downstream of effects may be on TFS in doing this (if it is even possible). Is there a way for me to allow the TFS deployer agent(s) to support build quality changes notices from multiple TFS collections?

Dec 9, 2011 at 10:31 PM


Support for multiple collections or servers is on the road map for TFS Deployer but in the mean time you should be able to achieve it with multiple instances on TFS Deployer on the same machine:

  • Each instance will need to be in its own folder
  • You will need to manually configure multiple entries in the Services management console
  • Either get each instance to listen on its own port number (eg 8881, 8882, etc) or each instance to use a url suffix on the same port (eg http://machine:8881/instanceA, http://machine:8881/instanceB) but this is untested.