Environment variables expansion fails if variable name contains dot/dash #57
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.
For version 2.5, environment variable names can contain dot or dashes. Project keys like $sonar.projectkey in Jenkins configuration are quite common.
New changes broke existing configuration if job is configured with project keys like $sonar.projectkey. Getting below error during build
"java.net.URISyntaxException: Illegal character in query at index 62: https://foo.com/api/events?resource=${sonar.projectKey}&format=json&categories=Alert "
Per Open Group , pretty much any character is allowed for environment variable name except equals. However we need to consider compatibility with all utilities as well.
This PR address issue with dot and/or dash characters in environment variable names.