|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-15117) env Variables can not b... [email protected] (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... [email protected] (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... [email protected] (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... [email protected] (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... [email protected] (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... [email protected] (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... [email protected] (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... [email protected] (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... [email protected] (JIRA)

I have the same issue but for linux environment variables.
During job execution I execute a shell script that sets an environment variable say GINI_VERSION.
When I enter this variable in the predefined parameters field like version=${GINI_VERSION} or $GINI_VERSION. In the next job the entire string is passed and the variable is not resolved.