fix(ci): Fix syntax in ADO variable use #18258
Merged
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
github-actions
bot
added
area: build
tylerbutler
approved these changes
Nov 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
We're using a mix of macro (
$()) and template expression (variables['Build.Reason']) syntax in a variable use in an ADO pipeline task, which is resulting in all pipelines not printing the value of the variable and instead having a/mnt/vss/_work/_temp/<id>.sh: line 44: variables[Build.Reason]: command not founderror. Example.Luckily, where we use the variable functionally (not just printing its value for troubleshooting) we were already using template expression syntax, so things were working correctly, we just weren't getting the value printed.
Reviewer Guidance
The review process is outlined on this wiki page.