New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[JENKINS-42082] Verify that you can put TEST in an env var name #167
Conversation
abayer
commented
Jul 6, 2017
- JENKINS issue(s):
- JENKINS-42082
- Description:
- Just verifying that this isn't an actual bug, at least as of now.
- Documentation changes:
- n/a
- Users/aliases to notify:
- @reviewbybees
This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐝
steps { | ||
echo "TEST_VAR is ${TEST_VAR}" | ||
echo "VAR_TEST is ${VAR_TEST}" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to be safe, should add
sh "echo SH_TEST_VAR is $TEST_VAR"
sh "echo SH_VAR_TEST is $VAR_TEST"
or similar.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐝
@@ -37,6 +37,8 @@ pipeline { | |||
steps { | |||
echo "TEST_VAR is ${TEST_VAR}" | |||
echo "VAR_TEST is ${VAR_TEST}" | |||
sh 'echo "TEST_VAR from shell is ${TEST_VAR}"' | |||
sh 'echo "VAR_TEST from shell is ${VAR_TEST}"' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, the ${}
are valid in bash but in this case unnecessary.
It might cause confusion that groovy is expected to expand it, at least I had to read it three times to get that :)