-
Bug
-
Resolution: Unresolved
-
Critical
-
None
On a jenkins node that has 1 executor that is trying to execute an upstream job via the "trigger/call builds on other projects" build step, the job hangs indefinately or until the user-supplied timeout is reached.
In the console for the main job, it shows:
Waiting for the completion of <name-of-upstream-project>
While the Jenkins dashboard shows the upstream project is trying to build, with the text:
(pending - Waiting for next available executor )
I would expect that the plugin would somehow be able to indicate to the jenkins node that only 1 executor is required.
- is duplicated by
-
JENKINS-26959 Waiting Job blocks executor causing deadlock
-
- Resolved
-
-
JENKINS-30302 Matrix parent takes executor slot and blocks children
-
- Resolved
-
[JENKINS-12290] Deadlock/Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |
Priority | Original: Blocker [ 1 ] | New: Major [ 3 ] |
Link |
New:
This issue is duplicated by |
Link |
New:
This issue is duplicated by |
Workflow | Original: JNJira [ 142612 ] | New: JNJira + In-Review [ 175727 ] |
Issue Type | Original: Improvement [ 4 ] | New: Bug [ 1 ] |
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Summary | Original: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor | New: Deadlock/Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor |