• Type: Improvement
• Resolution: Cannot Reproduce
• Priority: Blocker
• Component/s: conditional-buildstep-plugin, run-condition-plugin
• Labels:

  • parallel
  • run-condition
• Environment:

  Master : Windows, Nodes : Linux

1. config.xml

   2 kB

   2012-05-08 06:18

2. sleep.xml

   1 kB

   2012-05-08 06:18

[JENKINS-13705] Builds are sequential when there is a "Run conditional step" build step, even though the project is configured for concurrent execution

Collapse comment: Dominik Bartholdi added a comment - 2016-06-16 06:43

Dominik Bartholdi added a comment - 2016-06-16 06:43

I'm not able to reproduce this. I tested it with a simple job only holding conditional buildsteps (single and multiple) - (within the conditions a shell step with "sleep 20" is executed). As long as there are more executors available, multiple executions are trigged in parallel.
The only reason for the described behaviour to happen I can think of, is when there is a build step within the condition that causes it. Please test which of the steps in your scenario this could cause and feel free to reopen this issue.

Expand comment: Dominik Bartholdi added a comment - 2016-06-16 06:43

Dominik Bartholdi added a comment - 2016-06-16 06:43 I'm not able to reproduce this. I tested it with a simple job only holding conditional buildsteps (single and multiple) - (within the conditions a shell step with "sleep 20" is executed). As long as there are more executors available, multiple executions are trigged in parallel. The only reason for the described behaviour to happen I can think of, is when there is a build step within the condition that causes it. Please test which of the steps in your scenario this could cause and feel free to reopen this issue.