[JIRA] (JENKINS-14108) Multiple parameterized upstreams with joined in one "blocked while.." job result in multiple executions rather one only

[cjo9...@java.net (JIRA)]

cjo9900 commented on JENKINS-14108 Multiple parameterized upstreams with joined in one "blocked while.." job result in multiple executions rather one only I have talked to Claus on the cause of this issue and found that the behaviour is caused by how the core handled the dependencies. The use case was Job A param trigger -> Job B1 Param trigger -\ \> Job B2 Param trigger -> Job C and parameters from jobs B1 and B2 passed to Job C are different. In older versions before Jenkins ~1.402, job C would be triggered only once so would imitate a join of B1 and B2. After 1.402 Job C would be triggered twice once with the parameters from Job B1 and once with parameters from Job B2 as these are different. In this case the join plugin cannot be used as the downstream job C required parameters from B1 and B2, and links upstream started that the join plugin cannot pass. Possible solution is to have a special ParameterAction that implements the QueueAction(returning false even if there are existing parameters) and FoldableAction interface allowing parameters to be combined into a single Action and build. Which should then allow this join behaviour to occur. However this may cause issues for other plugins wanting to get the ParametersAction.

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