This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
Pipeline name can contain characters not allowed for package id #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
After investigating why this task would not work I realized it was because of characters not allowed.
The problem lies in that pipeline names, which are defined as
Build.DefinitionNamein the pipeline, have a more relaxed set of rules of allowed characters than package ids for the universal package feed.There's already a regular expression removing empty space, but that is not enough.
Since it is not possible to apply your own name for the package id in the task input, this works a quick fix removing all the characters not allowed in the package id according to Azure DevOps documentation.