#27318·jenkins

Support starting leased nodes with throttle concurrent builds when there are remaining free executor on already started node with same label

Author: apupierCreated Sep 1, 2026Updated Sep 8, 2026

What feature do you want to see added?

Support starting leased nodes with throttle concurrent builds when there are remaining free executor on already started node with same label

it is currently working when there is no free executors, but not working when there are free executors.

Context:

  • Pipeline A with throttle category my-cat can play on node with label label1
  • Pipeline B with throttle category my-cat can play on node with label label1
  • Leased Node 1 with label label1 and 2 executors
  • Leased Node 2 with label label1 and 2 executors

Current Sequence:

  • pipeline A is triggered
  • Leased Node 1 is starting
  • pipeline A is executing on leased node 1
  • pipeline B is triggered
  • pipeline B is awaiting a free executor (Leased Node 1 has 1 free executor but throttle is preventing to use it, the free executor is preventing leased node 2 to start)
  • pipeline A finish
  • pipeline B is executing on leased node 1

Expected sequence:

  • pipeline A is triggered
  • Leased Node 1 is starting
  • pipeline A is executing on leased node 1
  • pipeline B is triggered (Leased Node 1 cannot be used due to the throttling)
  • Leased Node 2 is starting
  • pipeline B is executing on leased Node 2

Real use case is experienced here:

Upstream changes

No response

Are you interested in contributing this feature?

No response