• 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

BalagiriPrasad S created issue - 2012-05-08 06:18

BalagiriPrasad S made changes - 2012-05-08 06:20

Description

Original: The reason for making "Invoke Maven Target" build step is not parallel may be because two concurrent maven calls can corrupt the repository. But when the two builds are happening on different nodes then jenkins should allow them. I am using nodelableparam to select different nodes, throttle Concurrent Builds configured to have 'Maximum Concurrent Builds Per Node' as 1. Attached the project files. In sleep.xml, update <host:port> with proper values

New: The reason for making "Invoke Maven Target" build step not parallel, may be because two concurrent maven calls can corrupt the repository. But when the two builds are happening on different nodes then jenkins should run them in parallel. I am using nodelableparam to select different nodes, throttle Concurrent Builds configured to have 'Maximum Concurrent Builds Per Node' as 1. Attached the project files. In sleep.xml, update <host:port> with proper values

BalagiriPrasad S made changes - 2012-05-28 10:24

Component/s		New: run-condition [ 16129 ]
Component/s	Original: core [ 15593 ]
Description	Original: The reason for making "Invoke Maven Target" build step not parallel, may be because two concurrent maven calls can corrupt the repository. But when the two builds are happening on different nodes then jenkins should run them in parallel. I am using nodelableparam to select different nodes, throttle Concurrent Builds configured to have 'Maximum Concurrent Builds Per Node' as 1. Attached the project files. In sleep.xml, update <host:port> with proper values	New: The description summary the problem. When there is "Run conditional step" then build on one node is waiting for the build on the other node complete, even though the project is configured for parallel builds.
Labels	Original: concurrent-build	New: parallel run-condition
Summary	Original: Builds are sequential when there is a "Invoke Maven Target" build step, even though the project is configured for concurrent execution	New: Builds are sequential when there is a "Run conditional step" build step, even though the project is configured for concurrent execution

Oleg Nenashev made changes - 2013-11-19 20:37

Component/s

New: conditional-buildstep [ 15947 ]

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.

Dominik Bartholdi made changes - 2016-06-16 06:43

Resolution		New: Cannot Reproduce [ 5 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Dominik Bartholdi made changes - 2016-06-16 06:44

Assignee

New: Dominik Bartholdi [ imod ]

R. Tyler Croy made changes - 2016-07-25 23:54

Workflow

Original: JNJira [ 144172 ]

New: JNJira + In-Review [ 190947 ]