|
||||||||
|
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/groups/opt_out.
This looks to me like it works as intended. The parameterized trigger only passes actual build parameters, not variables defined as environment variables.
In many of my builds, I have a few parameters at most, and often dozens of environment variables to configure generic build scripts to the specific job (like paths to certain programs in specific versions).
An easy workaround for this issue also exists: Just add a "predefined parameters" element from the parameterized build trigger plugin, and enter PARAM_SLAVE=$PARAM_SLAVE to override the default value of the slave. Skip the "current build parameters" entirely, it's simply not what you want.