Open OmarBazaraa opened 1 year ago
Using AzureWebApp
instead of AzureRmWebAppDeployment
fixed the problem for me.
I'm experiencing this problem too. I deploy to a virtual directory, and I see AzureWebApp has a parameter to accept a custom deployment directory but it's not available in the GUI. Is there a way to set this parameter with a GUI release pipeline?
workaround: I'm able to rename my packages as .war to get the custom deployment folder to show in the GUI. I used to use /api but need to do ../api since it tries to put it in a webapps folder when deployed.
I was getting similar error, but my pipeline was a classic not yaml. After trying different solutions, these were the steps that resolved my issue:
Task name
AzureRmWebAppDeployment
Task version
4
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
Azure DevOps Server (Please specify exact version in the textbox below)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows
Question
From April 28th, our Azure DevOps release pipeline that uses
AzureRmWebAppDeployment@4
task started to fail with the following logs:And this is the task definition that has been working for over 2 years already:
I have checked the Azure DevOps service connection
My-Central-Connection
and it is still active (none of its secrets has expired).Can you please assist on what should be done to fix the issue? Our pipeline is blocked for a week now.
Thanks