Fix package resolutions with spaces in names #1694
Merged
Conversation
This file contains hidden or 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
mik-ky
force-pushed
the
fnm/expand-path-vars-encoding
branch
from
5d8e6fb to
7bdcec2
Compare
mik-ky
force-pushed
the
fnm/expand-path-vars-encoding
branch
from
7bdcec2 to
f762ad1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In Azure devops, if you have a repository with spaces in the name (e.g. "ADO Repository") and you source a script from the git, Octopus isn't able to find the package.
Unlike github repositories where spaces are replaced with
-, ADO encodes the spaces to%20. Then in octopus, the package name will be encoded once again, which turns the already encoded space%20into%2520. There isn't a great way to deal with this distinction yet, so I've added two cases to handle for both space and double encoded space.[sc-131205]