-
New Feature
-
Resolution: Postponed
-
Major
-
None
Triggered jobs should run synchronously as mentioned or listed when using the "Trigger/Call builds on another project" item. This will help to run or build in sequence controlled manner which user is defined.
Currently Jenkins picks up job randomly. Using Jenkins ver. 1.491
[JENKINS-17286] Triggered jobs should run synchronously as mentioned or listed when using the "Trigger/Call builds on another project" item
siddu D
added a comment - The Executor value is set to 5 siddu D
added a comment - it works with executor 2. Is this expected behavior? If so then it is good to have option called serial and concurrent. If the option is serial then jobs should get triggered in the order as mentioned in the projects list serially one after another once the job is completed. When option is concurrent then it is not required to maintain the project order given that executor is set more as per the requirement.
siddu D
added a comment - it works with executor 2. Is this expected behavior? If so then it is good to have option called serial and concurrent. If the option is serial then jobs should get triggered in the order as mentioned in the projects list serially one after another once the job is completed. When option is concurrent then it is not required to maintain the project order given that executor is set more as per the requirement. Closing issue as part of tikal-multijob-plugin issues cleanup.
If still relevant, please open a matching issue in https://github.com/jenkinsci/tikal-multijob-plugin/issues (you can refer to this issue in its description)
To Explain in detail:
Suppose if you mention list of projects like a,b,c. The order is not maintained even after selecting "Block until the triggered projects finish their builds". And it is observed that it will not run builds synchronously. All the listed projects gets triggered.