This project is read-only.

TFS Deployer

Rating:        Based on 5 ratings
Reviewed:  5 reviews
Downloads: 4285
Change Set: 54837
Released: Jan 12, 2011
Updated: Jan 11, 2011 by jstangroome
Dev status: Stable Help Icon


application, 178K, uploaded Jan 11, 2011 - 4285 downloads

Release Notes

Release build from changeset 54837

Important: This release contains breaking changes
The old TFS 2005 $TfsDeployerBuildData variable is no longer available to PowerShell deployment scripts.
  • Added a script to the Samples folder simulate the TFS Deployer environment outside of TFS Deployer for easier testing.
  • Fixed spelling error in the $TfsDeployerBuildDetail.BuildDefinition.Process.Parameters property name.
  • Added support for queuing scripts to be processed in series instead of parallel using a Queue attribute in the DeploymentMappings.xml.
  • Multiple mappings matching a single event will be now be processed in parallel by default.
  • The build original and new quality values passed to PowerShell come from the TFS event instead of the mapping configuration.
  • NotificationAddress is no longer required in a mapping configuration if emails are not desired.
  • Fixed a bug preventing sending of the success email if the TFS Deployer service account does not have permission to retain builds.
  • Fixed missing script output prior to errors under some conditions.
  • Fixed support for script paths containing spaces, apostrophes, dollar-signs, and backticks.
  • Moved old configuration signing arguments out of TfsDeployer.exe and into PowerShell scripts.
  • Fixed batch script deployment error when TimeoutSeconds attribute is not specified in Mapping element.

Reviews for this release

by its description if I could get it working it would easily earn 5 stars, but there are no installation configuration instructions available. With Powerscript and TFS tie in, I really think this is not reasonable.
by hintzen on May 11, 2012 at 4:45 AM
It just works. Really simple, bare bones, this is exactly what is needed. You can do all your fancy install stuff in PowerShell V3 scripts. Just did a deployment on TFS 2012
by sanjay10 on Aug 19, 2013 at 7:38 PM
One of the better little tools I keep in my toolbox. Using this in conjuntion with TFS build qualities I was able to remove a lot of admin rights to various DEV and QA servers for developers and force them to deploy through the TFS interface. End result was better automated builds and an assurance that what we were deploying was at least checked into TFS source control. Must have for CI.
by Fogbound on Oct 29, 2012 at 6:19 PM
Overall I am very pleased with this product, and I have not had any problems and it has worked well.
by crazyoldman on Jun 21, 2012 at 8:06 PM
Much more stable than previous releases. We are running multiple TFS Deployer instances in different parts of the country and it runs very well with minimal problems.
by cooperba3 on Jun 8, 2011 at 10:22 PM