Tasks for Azure Pipelines
If you are not the TFS team project collection administrator, make sure that you have been added as an agent pool administrator at All Pools level. For more information, see Agent pools.
Download the attached PowerShell script VsTest-2.157.3.ps1.
On one your TFS Application Tiers, open a PowerShell console, and then change the current location to the directory where you downloaded the .ps1 file in step 2.
To verify that your execution policy allows for the execution of installation scripts, run the following command line:
Set-ExecutionPolicy Unrestricted -Scope Process -Force
.\VsTest-2.157.3.ps1 -CollectionUrl http://myserver:8080/tfs/DefaultCollection
If you are not the TFS team project collection administrator, make sure that you have been added as an agent pool administrator at All Pools level. For more information, see Agent pools.
Download the attached PowerShell script Bash-3.142.2.ps1.
On one your TFS Application Tiers, open a PowerShell console, and then change the current location to the directory where you downloaded the .ps1 file in step 2.
To verify that your execution policy allows for the execution of installation scripts, run the following command line:
Set-ExecutionPolicy Unrestricted -Scope Process -Force
.\Bash-3.142.2.ps1 -CollectionUrl http://myserver:8080/tfs/DefaultCollection
When you use Team Foundation Server (TFS) 2017 RTM or Update 1, and the MSBuild or VSBuild task with Visual Studio 2017 Update 2 or higher. The task is unable to find the installed location of msbuild.exe.
The preferred resolution is to update to TFS 2017 Update 2 or higher.
Otherwise the steps below can be used to update the MSBuild and VSBuild tasks:
If you are not the TFS team project collection administrator, make sure that you have been added as an agent pool administrator at All Pools level. For more information, see Agent pools.
Download the attached PowerShell script Update-MSBuild_VSBuild_TFS2017RTM_thru_U1.ps1.
On one your TFS Application Tiers, open a PowerShell console, and then change the current location to the directory where you downloaded the .ps1 file in step 2.
To verify that your execution policy allows for the execution of installation scripts, run the following command line:
Set-ExecutionPolicy Unrestricted -Scope Process -Force
.\Update-MSBuild_VSBuild_TFS2017RTM_thru_U1.ps1 -CollectionUrl http://myserver:8080/tfs/DefaultCollection
When using TFS 2017 RTM or TFS 2017 Update 1, you may also be experiencing an error when queuing the build:
No agent could be found with the following capabilities: msbuild [...]
or
No agent could be found with the following capabilities: visualstudio [...]
To resolve the capability error, you can either add the missing capability as a user capability or you can download and install the TFS 2017 Update 2 agent.
Hotfix for /mt issue on pre 2008 R2
Use TFX to upload to your account. You will need to follow the instructions on the TFX repo to:
tfx build tasks upload command
Details on each of the steps are listed on the TFX repo and in or linked from the README.md
Hotfix created from branch: refs/heads/releases/m118 Commit: 1fb1744926d3f04bf7afbb63c5fac464dc8efe2e
The purpose of this hotfix is to fix the bug calling vswhere (does not find build tools product) and vs fallback issues
Use TFX to upload to your account. You will need to follow the instructions on the TFX repo to:
tfx build tasks upload command
Details on each of the steps are listed on the TFX repo and in or linked from the README.md
Built from PR https://github.com/Microsoft/vsts-tasks/pull/3457
Use TFX to upload to your account. You will need to follow the instructions on the TFX repo to:
tfx build tasks upload command
Details on each of the steps are listed on the TFX repo and in or linked from the README.md
Xamarin Android task from releases/m109 at commit e922c298ac2d715c93af38dbee7976948052b037