[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

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

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.

---
Originally reported by garen, imported from: 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

• assignee: huybrechts
  
• status: Open
  
• priority: Critical
  
• component(s): parameterized-trigger-plugin
  
• resolution: Unresolved
  
• votes: 38
  
• watchers: 41
  
• imported: 2025-12-07
  

Raw content of original issue

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.