This project is read-only.

TFS Deployer Configuration

Aug 5, 2010 at 3:43 PM
I downloaded the TFS Deployer 1.2 for TFS 2010 (Beta) and noticed that the TFS Deployer configuration file has changed between versions. I’m attempting to set up TFS Deployer to work with Team Foundation Server 2010 but was not sure how to set some of the configuration values. Specifically, how do the TeamProjectCollectionUri and the BaseAddress relate to each other? And what should the BaseAddress value be for the typical TFS Deployer installation? Thanks.
Aug 7, 2010 at 2:42 PM


TeamProjectCollectionUri is the address of the project collection that TFS Deployer will connect to and subscribed to build status events for. If you are using the "DefaultCollection" that gets created during a TFS 2010 install on a server called "mytfs" with default the ports, the value of this setting would be "http://mytfs:8080/tfs/DefaultCollection". If you have multiple Project Collections, you will need multiple TFS Deployer instances.

The BaseAddress determines the url on which TFS Deployer will listen for build status events. Whatever you choose, the TFS Deployer service account will need permission to listen at that address. In current versions of Windows this is managed via "netsh http add urlacl /?". TFS Deployer will also pass this address to TFS when it subscribes to build events. TFS will then use this to connect to TFS Deployer when the build status changes, therefore the url must be resolvable from the TFS application-tier. Aside from changing "MyHostname" in the default TfsDeployer.exe.config file to match the name of the machine TFS Deployer is installed on, you shouldn't need to change this unless it clashes with other services on the same machine.  This behaviour is unchanged from previous versions of TFS Deployer and TFS.



Aug 13, 2010 at 5:49 PM

Thanks for the reply.  That helped clear up some of the confusion.