|
||||||||
|
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.
Hi,
Thanks for looking at this issue.
Your test scenario also works for me. I see now that my steps to reproduce are not completely accurate.
The "upstream" maven project is also parameterized with 1 parameter (otherparam)
this has ${POM_ARTIFACTID}-${BUILD_ID} configured as the default value
then this projects triggers downstream with
myparam=${otherparam}
The downstream build outputs ${POM_ARTIFACT_ID}-2014-12-07_09-57-07 in the console
So the expansion is working for "normal" jenkins variables like ${BUILD_ID} but not for the maven variables
I am using jenkins 1.564 , maven-plugin 2.7, parameterized-trigger-plugin 2.24