azureremwebappdeploymentv3 broken after 3.175.2 update

[slaanish]

Required Information

Entering this information will route you directly to the right team and expedite traction.

Question, Bug, or Feature?
Type: Bug
Enter Task Name: azurermwebappdeplymentv3

list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks

Environment

• Server - Azure Pipelines or TFS on-premises?

• Azure Pipelines

• Agent - Hosted or Private:

  • Private Agent Windows Server

Issue Description

azurermwebappdeplymentv3 After updating to version 3.175.2 deploys started failing not being able to find msdeploy. There is now a new folder in the task version directory named webdeployment-common. The error claims to be looking for msdeploy in this new directory. There is no MSDeploy3.6 directory there. It is in the base (3.xxxx) directory like it always has been.

Task logs

2020-09-16T22:35:56.5304279Z ##[debug]Absolute path for pathSegments: X:\R1_work_tasks\AzureRmWebAppDeployment_497d490f-eea7-4f2b-ab94-48d9c1acdcb1\3.175.2\webdeployment-common\MSDeploy3.6/msdeploy = X:\R1_work_tasks\AzureRmWebAppDeployment_497d490f-eea7-4f2b-ab94-48d9c1acdcb1\3.175.2\webdeployment-common\MSDeploy3.6\msdeploy
2020-09-16T22:35:56.5305554Z ##[debug]Absolute path for pathSegments: C:\Windows\system32/msdeploy = C:\Windows\system32\msdeploy
2020-09-16T22:35:56.5307363Z ##[debug]Absolute path for pathSegments: C:\Windows/msdeploy = C:\Windows\msdeploy
2020-09-16T22:35:56.5308645Z ##[debug]Absolute path for pathSegments: C:\Windows\System32\Wbem/msdeploy = C:\Windows\System32\Wbem\msdeploy
2020-09-16T22:35:56.5310124Z ##[debug]Absolute path for pathSegments: C:\Windows\System32\WindowsPowerShell\v1.0/msdeploy = C:\Windows\System32\WindowsPowerShell\v1.0\msdeploy
2020-09-16T22:35:56.5312457Z ##[debug]Absolute path for pathSegments: C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn/msdeploy = C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn\msdeploy
2020-09-16T22:35:56.5313382Z ##[debug]Absolute path for pathSegments: C:\ProgramData\chocolatey\bin/msdeploy = C:\ProgramData\chocolatey\bin\msdeploy
2020-09-16T22:35:56.5314706Z ##[debug]Absolute path for pathSegments: C:\Users\USER\AppData\Local\Microsoft\WindowsApps/msdeploy = C:\Users\USER\AppData\Local\Microsoft\WindowsApps\msdeploy
2020-09-16T22:35:56.5316887Z ##[debug]check path : null

Troubleshooting

I copied the MSDeploy3.6 folder into the webdeployment-common directory and it made it happy. I do not feel this if the proper fix, but it got it going.

Error logs

[20shivangi]

@damccorm Can you please check this, I think moving webappdeployment-common folder within the task has broken our code

[d-burr]

@chshrikh @N-Usha @nadesu we are also being effected by this issued, is there an ETA on it being resolved?

[trreeves]

@chshrikh @N-Usha @nadesu This is seriously affecting multiple teams in our organisation. A prompt fix would be gratefully received.

[nadesu]

@20shivangi, @damccorm - What is the expected ETA for the fix?

[damccorm]

Sorry, didn't mean to close - this should be fixed in master, it should roll out with the next sprint payload over the next 3 weeks

[nulltoken]

FWIW, upgrading to v4 solved the issue for us

[20shivangi]

@slaanish Yes, you can either upgrade your task to use V4 version or wait for at least 3 weeks till the fix reaches to your account. Thank you for your patience.

[20shivangi]

Closing this issue. Please wait for the fix to reach your account.
Feel free to reopen it if face any further issue

[damccorm]

FWIW we actually ended up rolling this fix out last night, so it should be everywhere now

[trreeves]

We really appreciated the prompt roll out of this fix. We had a lot of teams to communicate with and a lot of noise to deal with. Thanks.