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

[de...@ikedam.jp (JIRA)]

ikedam commented on JENKINS-25936 Maven environment variables are not expanded when triggering another project. Launcher expands all variables with each other (to be exact, Launcher#inherit and EnvVars#overrideExpandingAll do). Launchers launch native processes, and this affects all plugins using native processes. For example, maven-plugin should expand uparam to parameterized-trigger-2014-12-08_08-14-23. In short, plugins without native processes and those with native processes expand variables in different ways. I think this is a limitation of Jenkins. Users should not trust the variable expantion by Jenkins, and should do in more concrete ways. I'll close this issue with Won't Fix in a week. You can file a new issue with its component "core".

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.