TFS Deployer

Updated Wiki: Home

jstangroome — Wed, 02 Jul 2008 12:17:31 GMT

Welcome

Welcome to the TFS Deployer project homepage, to see what this project is all about please refer to our project description.

Project Description

TFS Deployer was originally released by Readify on the 16th of December 2006. This CodePlex project exists to further its development beyond support for Team Foundation Server 2005 and address some of the shortcomings within the software.

By way of explaination, TFS Deployer interfaces the Team Foundation Server build store with PowerShell allowing script execution to be triggered across multiple machines when a user transitions the quality indicator of a build from one state to another.

TFS Deployer is installed like an agent piece of software on deployment targets and those targets listen for the event notifications from TFS. When received they contact TFS to determine whether they should take action, and if they should they download the scripts from the version control repository.

TFS Deployer integrates with PowerShell to provide scripters with access to the BuildData object from the TFS object model so that they can determine where to pull down build outputs from so that they can be automatically deployed in an enterprise environment.

Positions Vacant

If you would like to help out with this project, please visit our Positions Vacant page.

Source code checked in, #13938

jstangroome — Sun, 29 Jun 2008 12:33:33 GMT

Adding initial support for shared deployment resources. Requires testing against TFS.

Source code checked in, #13903

jstangroome — Sat, 28 Jun 2008 10:06:06 GMT

Clarifying variable naming with respect to server paths versus local paths.

CREATED RELEASE: TFS Deployer 1.1 (BETA2) (May 14, 2008)

Wed, 14 May 2008 04:27:00 GMT

This is a BETA2 release of TFS Deployer 1.1. It is designed to work against Team Foundation Server 2008 but without too many other architectural changes. A number of long standing bugs have been fixed, so if you can use this, highly recommended! The second BETA addresses one issue in particular around the code being explicitly compiled for the x86 architecture which means (ironically) that you can then use it on an x64 machine.

RELEASED: TFS Deployer 1.1 (BETA2) (May 14, 2008)

Wed, 14 May 2008 04:27:00 GMT

Source code checked in

MitchDenny — Wed, 14 May 2008 04:03:47 GMT

Preparing a BETA2 version of TFS Deployer 1.1 - found a bug where we weren't compiling as x86 which causes a problem on x64 architectures because the TFC libraries complain.

NEW POST: TfsDeployer -? : What are those extra parameters ?

cyberjp — Mon, 21 Apr 2008 02:17:47 GMT

Hi Jason,

Thanks for taking the time to answer my question.

Thank you for your examples, they helped very much !

By the way, congratulations for TfsDeployer, it's a wonderfull tool.

J-P

COMMENTED ISSUE: Command Line help shows incorrect options

jstangroome — Sat, 19 Apr 2008 02:20:29 GMT

/CreateKeyFile and /EncryptDeploymentFile are readonly properties on the CommandLine class and should not show in the usage output.
Comments: Fixed on changeset 9538

Source code checked in

jstangroome — Sat, 19 Apr 2008 02:20:25 GMT

CommandLineParser now ignores read only properties. work item: 1894

Source code checked in

jstangroome — Sat, 19 Apr 2008 02:14:24 GMT

Correcting spelling errors.

CREATED ISSUE: Command Line help shows incorrect options

jstangroome — Sat, 19 Apr 2008 02:12:40 GMT

/CreateKeyFile and /EncryptDeploymentFile are readonly properties on the CommandLine class and should not show in the usage output.

NEW POST: TfsDeployer -? : What are those extra parameters ?

jstangroome — Sat, 19 Apr 2008 02:11:28 GMT

Firstly /CreateKeyFile and /EncryptDeploymentFile are showing due to a bug and will either be ignored or crash the app. The remainder exist to digitally sign deployment mapping files to prevent uinauthorized tampering. Basic usage examples follow, the first to create a key then use it to sign the mapping file:

tfsdeployer.exe /g:MyKeyFile.key
tfsdeployer.exe /k:MyKeyFile.key /m:DeploymentMappings.xml

The second example creates a new key and signs the mapping file in one step:

tfsdeployer.exe /g:MyKeyFile.key /m:DeploymentMappings.xml

Once you have a key file and an encrypted mapping file. You can check the signed mapping file into source control and keep the key file securely on the Tfs Deployer machine. You then need to edit the TfsDeployer.exe.config file and change the KeyFile setting within to refer to the location of the key file and also change the SignDeploymentMappingFile setting to "True". Then restart the Tfs Deployer sevice.

If you enable signing in your Tfs Deployer config, all mapping files will need to be signed.

Does this help?

Regards,

--
Jason

NEW POST: TfsDeployer -? : What are those extra parameters ?

cyberjp — Fri, 18 Apr 2008 15:52:15 GMT

I type the command : TfsDeployer -? and I get extra parameters.

Can you give more information on those parameters and an example of how to use them ?

TFSDeployer v1.0.0.0
Copyright © 2006

Usage: TFSDeployer.exe @argfile /CreateKeyFile[+
/EncyptDeploymentFile[+ /m:<value> /k:<value> /g:<value> [/hel
p|?|h]
/version

@argfile Read arguments from a file.
/CreateKeyFile+ CreateKeyFile
/EncyptDeploymentFile+ EncyptDeploymentFile
/m:<value> Deployment Mapping File Name
/k:<value> Key File Name
/g:<value> Create Key File
/help Show usage.
/version Show version.

NEW POST: Configure TFSDeployer

am_karthik — Thu, 10 Apr 2008 11:48:04 GMT

I am getting a strange error,
I have registered the service in VS2005
I tried registering in both the servers (TFS server and Build server)
But still I cant make it work.
But I get email notications abt change of status.

I checked the event subscription and found the service availabale, but also get the below error.
Can Anyone throw some light on it

http://:8899/BuildStatusChangeEvent/BuildStatusChangeEvent
=============================================

- <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
- <s:Body>
- <s:Fault>
<faultcode xmlns:a="http://schemas.microsoft.com/ws/2005/05/addressing/none">a:ActionNotSupported</faultcode>

<faultstring xml:lang="en-GB">The message with Action '' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).</faultstring>
</s:Fault>
</s:Body>
</s:Envelope>

NEW POST: TFSDeployer to log on as System Account

Trennum — Thu, 10 Apr 2008 00:50:11 GMT

I'm trying to edit the properties of the TFSDeployer service to allow it to run under the local system and allow the service to interact with the desktop. Whenever I try to make this change I am unable to start the sservice back up again. Has anyone experienced this or have any potential solutions I could try?

Thanks

Source code checked in

jstangroome — Tue, 08 Apr 2008 12:55:33 GMT

adding support to set or clear Retain Build setting on successful deployment.

Patch Applied

jstangroome — Sat, 05 Apr 2008 04:21:31 GMT

jstangroome has applied patch #1073.

Comment:
Good idea.

Source code checked in

jstangroome — Sat, 05 Apr 2008 04:21:09 GMT

Integrating Grant Holliday's patch for multiple notification addresses.

CLOSED ISSUE: Incorrect Bindings When Installed with Team Explorer 2008

jstangroome — Sat, 05 Apr 2008 04:12:44 GMT

When installing TFS Deployer on a machine with Team Explorer 2008, you will be presented with incorrect bindings and will receive the following error when running in the debug ( -d ) mode:

System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Team
Foundation.VersionControl.Common.Integration, Version= 8.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot f
ind the file specified.
File name: 'Microsoft.TeamFoundation.VersionControl.Common.Integration , Version=
8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
at Readify.Useful.TeamFoundation.Common.Listener.TfsListener.RegisterEventLis
teners()
at Readify.Useful.TeamFoundation.Common.Listener.TfsListener.Start ()
at TfsDeployer.Program.OnStart(String[] args)
at TfsDeployer.Program.Main(String[] args)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\M
icrosoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure lo
gging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fus
ion!EnableLog].

To work around this issue in the meantime, add the following section to the TFSDeployer.exe.config file:

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.TeamFoundation.VersionControl.Client " publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion="8.0.0.0" newVersion="9.0.0.0 "/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.TeamFoundation.VersionControl.Common.Integration" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion="8.0.0.0" newVersion="9.0.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.TeamFoundation.Build.Common" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion=" 8.0.0.0" newVersion="9.0.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.TeamFoundation" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion="8.0.0.0" newVersion="9.0.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.TeamFoundation.Client" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion=" 8.0.0.0" newVersion="9.0.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

CLOSED FEATURE: Include machine name in alert e-mail body

jstangroome — Sat, 05 Apr 2008 04:12:44 GMT

Although the target machine name is in the TFS Deployer alert e-mail it would be good to include it in the e-mail body too.