[JIRA] [parameterized-trigger-plugin] (JENKINS-25936) Maven environment variables are not expanded when triggering another project.

Sun, 07 Dec 2014 15:48:17 -0800

ikedam commented on Bug JENKINS-25936

I succeeded to reproduce that.
Jenkins looks resolve variables each other in first.

Running following scripts from Manage Jenkins > Script Console

Jenkins.instance.getItemByFullName("upstream").getLastBuild().getEnvironment();

outputs

POM_ARTIFACTID=parameterized-trigger
uparam=${POM_ARTIFACTID}-2014-12-08_08-14-23

, and it might be a problem in Jenkins core.



I should see why it works for Execute shell or Execute Windows batch command (How do they access environments?)



Anyway, please try to not to reference variables from other variables, as each-other-resolving looks unstable.
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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to