|
||||||||
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)
looks like the issue is fixed in commit
https://github.com/jenkinsci/parameterized-trigger-plugin/commit/16586248c382ef417e0aaa1d2cdb00baee87ec18
for inclusion into version 2.17.
Note you need to specify the predefined parameters using the myJobName=$JOB_NAME instead of the windows %JOB_NAME% style, as mentioned in the help "Current build parameters and/or environment variables can be used in form: ${PARAM} or $PARAM."
You can test using the built version at https://jenkins.ci.cloudbees.com/job/plugins/job/parameterized-trigger-plugin/1/org.jenkins-ci.plugins$parameterized-trigger/