magielonczyk and the community provide practical approaches to reverting an AzureRmWebAppDeployment task to an earlier version in Azure DevOps, including forking, publishing custom tasks, and YAML version pinning.

Reverting AzureRmWebAppDeployment Task Version in Azure Pipelines

Author: magielonczyk

Question

Is it possible to revert the AzureRmWebAppDeployment (V4) pipeline task from version 3.259.0 to 3.249.0? The user references npm registry details and tfx usage:

Azure Pipelines Tasks - npm registry link
Using tfx build tasks with direct task API URL to a specific version.

Community Insights and Replies

Fork and Publish Approach

You can fork the task repository, build your version, then publish it to your Azure DevOps organization.
Afterwards, update your pipelines to reference the custom (older) task.

Direct Version Pinning in YAML

In YAML pipelines, you can specify a particular version directly:
```
- task: AzureRmWebAppDeployment@3.249.0
```
As long as Microsoft hasn’t removed the prior version, this will work for major version changes (not always possible with minor ones).

Using tfx

tfx can be used for managing and uploading specific task versions if you have access.

Workarounds

If reverting isn’t possible or sustainable, another option is to use custom PowerShell or Python scripts instead of relying on changing Microsoft tasks. This can give more control and prevent future unexpected breaks.

Reporting Issues

If there are breaking changes or issues with the latest version, report them on the Azure Pipelines Tasks GitHub repo with details. The maintainers may assist or resolve the issue.

Version Reference

The post included a detailed list of published task versions and their release dates for tracking available versions.

Summary Steps

Try pinning the task version in YAML (AzureRmWebAppDeployment@3.249.0).
Fork, build, and publish the prior version if necessary.
Consider alternatives such as custom deployment scripts for stability.
Report incompatibilities or issues to Microsoft via GitHub.

This post appeared first on “Reddit Azure DevOps”. Read the entire article here