-
Bug
-
Resolution: Fixed
-
Major
-
None
-
parameterized-trigger-plugin version 2.11
Jenkins ver. 1.436
Steps to reproduce
- Create a job and add a new "Trigger/call builds on other projects" step
- For the "Projects to build" parameter, give a project name that is parameterized
- Run the job once with one set of parameters --> correct project is executed
- Run the job again with another set of parameters --> same project as before is executed, instead of the new one
For example
- I have jobs with names of the form ${SELECTED_PROJECT}-war-${CODE_VERSION}, e.g. datatool-war-trunk, chat-war-qa, etc
- I create another job with SELECTED_PROJECT and CODE_VERSION as parameters
- Within this job, I add a parameterized trigger step with ${SELECTED_PROJECT}-war-${CODE_VERSION} as the project name
- I run the build once with SELECTED_PROJECT=datatool,CODE_VERSION=trunk
- datatool-war-trunk is executed as expected
- I run the build again with SELECTED_PROJECT=chat,CODE_VERSION=qa
- datatool-war-trunk is triggered--NOT chat-war-qa as expected
Possible fix
I'm able to fix this by removing the "caching" for projectList within BuildTriggerConfig.java: see here
Can you retry this test with 2.15, as the caching of the project list was removed in this version.
https://github.com/jenkinsci/parameterized-trigger-plugin/commit/6d8ffe980777dd7cccc1f9481e374c5861aebda8