-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Minor
-
Component/s: parameterized-trigger-plugin
-
Environment:parameterized-trigger-plugin version 2.10
Steps to reproduce:
Set up multiple (eg. six) blocking trigger builder configs in one trigger buildstep that each triggers a project (the first one triggers "project1", the second one triggers "project2", etc.)
Expected console log output should be:
Started by user SYSTEM Waiting for the completion of project1 project1 #1 completed. Result was SUCCESS Waiting for the completion of project2 project2 #1 completed. Result was SUCCESS Waiting for the completion of project3 project3 #1 completed. Result was SUCCESS Waiting for the completion of project4 project4 #1 completed. Result was SUCCESS Waiting for the completion of project5 project5 #1 completed. Result was SUCCESS Waiting for the completion of project6 project6 #1 completed. Result was SUCCESS Finished: SUCCESS
Actual output is something like this:
Started by user SYSTEM Waiting for the completion of project5 project5 #1 completed. Result was SUCCESS Waiting for the completion of project1 project1 #1 completed. Result was SUCCESS Waiting for the completion of project3 project3 #1 completed. Result was SUCCESS Waiting for the completion of project2 project2 #1 completed. Result was SUCCESS Waiting for the completion of project4 project4 #1 completed. Result was SUCCESS Waiting for the completion of project6 project6 #1 completed. Result was SUCCESS Finished: SUCCESS
The order of the project's completion might actually depend on where they are executed (different slaves), different system loads, etc,
but thats not the reason for the non-deterministic order of the projects in the console log. It's simply because all the configs are
added to a hashmap before they are processed.
I think it's more reasonable to show the projects in the log output in the same order they are defined.
