|
||||||||
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... i.rei...@dkfz.de (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... i.rei...@dkfz.de (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... i.rei...@dkfz.de (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... i.rei...@dkfz.de (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... m...@steinwelberg.nl (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... i.rei...@dkfz.de (JIRA)
- [JIRA] (JENKINS-15117) env Variables can ... m...@steinwelberg.nl (JIRA)
@Stein Welberg
if you want to use variables that are set in a shell, you will need to add them to the Jenkins build Environment first, otherwise they will only be available for the life of that shell session (buildstep).
You can do this by writing them to a properties file (KEY=VALUE format) in the workspace and then using the EnvInject plugin[1] to add them from that as the next build step, which will make the variables available from that point on.
[1] https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin