[JENKINS-36793] Need Support to queue when node is not a direct input parameter

Hi,
Probelm:
There are certain jobs that will run on master and use node as inputs internally(backend),when we run multiple jobs on master with same node as inputs, right now all will get executed irrespective of that node is already used.

Suggested/Needed Solution:
One solution would be using Node label parameter plugin, but when we choose that, job will get scheduled in the node rather than master which is expected, as it ignores "Restrict where this project can be run" option which is by design, it would be good to have this enabled in special condition like this.

Or please suggest an suitable alternative.

Thanks in advance.

Originally reported by sathnaga86, imported from: Need Support to queue when node is not a direct input parameter

• status: Open
• priority: Critical
• component(s): nodelabelparameter-plugin
• resolution: Unresolved
• votes: 0
• watchers: 3
• imported: 20251210-235911

Raw content of original issue

Hi, 
Probelm:
There are certain jobs that will run on master and use node as inputs internally(backend),when we run multiple jobs on master with same node as inputs, right now all will get executed irrespective of that node is already used.

Suggested/Needed Solution:
One solution would be using Node label parameter plugin, but when we choose that, job will get scheduled in the node rather than master which is expected, as it ignores  "Restrict where this project can be run" option which is by design, it would be good to have this enabled in special condition like this.

Or please suggest an suitable alternative.

Thanks in advance.

Jenkins 2.0, 	<br/>
Node and Label parameter plugin 1.7.2

Start by reproducing the scheduling behavior described with Jenkins 2.0 and Node and Label Parameter plugin 1.7.2, then inspect the nodelabelparameter-plugin entry points for node selection and job queueing. Done means jobs running on the master can use an internal node input without concurrent jobs using the same node executing simultaneously, while preserving the project's run restriction.