Question

We are using TFSDeployer to listen to build quality changes and deploy to our staging environment when it transitions to ‘Staging’.

I’d like to have it go ahead and update all of the other builds that have a currently build quality of ‘Staging’ to be ‘Rejected’.

This appears to be something that needs to happen inside the PowerShell script which looks like:

$droplocation = $TfsDeployerBuildData.DropLocation ECHO $droplocation  $websourcepath = $droplocation + '\Release\_PublishedWebsites\CS.Public.WebApplication\' $webdestinationpath = '\\vmwebstg\WebRoot\CreditSolutions\'  new-item -force -path $webdestinationpath -itemtype 'directory' get-childitem $webdestinationpath | remove-item -force -recurse get-childitem $websourcepath | copy-item -force -recurse -destination $webdestinationpath  $configFile = $webdestinationpath + 'web.development.config' remove-item $configFile -force  $configFile = $webdestinationpath + 'web.staging.config' $configFileDest = $webdestinationpath + 'web.config' move-item $configFile $configFileDest -force 

So, how can I do this?

Answer 1

First add the Get-tfs function to your script:

function get-tfs (     [string] $serverName = $(Throw 'serverName is required') ) {     # load the required dll     [void][System.Reflection.Assembly]::LoadWithPartialName('Microsoft.TeamFoundation.Client')      $propertiesToAdd = (         ('VCS', 'Microsoft.TeamFoundation.VersionControl.Client', 'Microsoft.TeamFoundation.VersionControl.Client.VersionControlServer'),         ('WIT', 'Microsoft.TeamFoundation.WorkItemTracking.Client', 'Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore'),         ('BS', 'Microsoft.TeamFoundation.Build.Common', 'Microsoft.TeamFoundation.Build.Proxy.BuildStore'),         ('CSS', 'Microsoft.TeamFoundation', 'Microsoft.TeamFoundation.Server.ICommonStructureService'),         ('GSS', 'Microsoft.TeamFoundation', 'Microsoft.TeamFoundation.Server.IGroupSecurityService')     )      # fetch the TFS instance, but add some useful properties to make life easier     # Make sure to 'promote' it to a psobject now to make later modification easier     [psobject] $tfs = [Microsoft.TeamFoundation.Client.TeamFoundationServerFactory]::GetServer($serverName)     foreach ($entry in $propertiesToAdd) {         $scriptBlock = '             [System.Reflection.Assembly]::LoadWithPartialName('{0}') > $null             $this.GetService([{1}])         ' -f $entry[1],$entry[2]         $tfs | add-member scriptproperty $entry[0] $ExecutionContext.InvokeCommand.NewScriptBlock($scriptBlock)     }     return $tfs } 

Next, instantiate the TFS object

$tfs = get-tfs http://YourTfsServer:8080 

Then find the builds with a build quality of ‘Staging’

$builds = $tfs.BS.GetListOfBuilds('Test Project', 'TestBuild') |  where {$_.BuildQuality -eq 'Staging'} 

Finally, update the quality of these builds

 foreach ($build in $builds) { $tfs.BS.UpdateBuildQuality($build.BuildUri, 'Rejected') } 

(I haven’t run this script yet, but you should be able to get it going without troubles)

More info on my blog: Using the Team Foundation Object Model with PowerShell

One last advice, if you update the Build quality from within the script that is running from TfsDeployer, you could end up with 2 script running at the same time if you have a mapping for the Staging –> Rejected transition!