|
||||||||
|
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.
This seems to be caused by the fix for JENKINS-22005. Reverting to 2.16 fixes the problem. I can reproduce the issue using the following steps:
1) Create a job job1 with a string parameter named param1.
2) Create a job job2 with a string parameter named param1.
3) Create a job job3 with a string parameter named param1.
4) Add a promotion process promotion1 to job3 with criteria 'Only when manually approved'. Add an action 'Trigger parameterized build on other projects' to the promotion which triggers job1 with predefined parameters 'param1=${param1}'.
5) Add a promotion process promotion2 to job3 with criteria 'When the following downstream projects build successfully' on downstream project job1. Add an action 'Trigger parameterized build on other projects' to the promotion which triggers job2 with predefined parameters 'param1=${param1}'.
6) Run job3 with param1=someString.
7) Manually approve promotion1. You will see that job1 is correctly run with param1=someString.
8) Promotion process promotion2 will now automatically start job2. But job2 will be run with param1=${param1} which is not correct.