Fix tag normalization for Azure Pipelines #4400
Open
+57
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Change the Azure Pipelines agent so it does not return tag names as branch names.
Related Issue
#4015
Motivation and Context
Azure Pipelines provides the name of the tag for which the pipeline has been triggered in
BUILD_SOURCEBRANCH
asrefs/tags/<tag>
. When we do not ignore the tags in the Azure Pipelines agent, the repository normalization will normalizethe tag name
refs/tags/<tag>
to the local branch nametags/<tag>
. This leads to an incorrect calculation of prerelease labels(e.g.
tags-v1.2.3-beta.1
) .A similar issue has been fixed for GitHub Actions in #2838.
How Has This Been Tested?
Unit tests have been added for the Azure Pipelines agent.
Checklist: