[JENKINS-11255] Port allocation from named dynamic pools

In some cases, it is necessary for a job to aquire a port from a pool of predefined ports (eg. for using an independent memcache connection to be able to flush it on each test setup).

Each pool should have a name and an enumerated list of port numbers.

If a job depends on a pool, it is blocked until any of the pool's port gets released.

If a job has finished, it releases the aquired port, just as it is implemented with the fixed port allocation strategy.

Allocating a fixed port should lock that port from getting aquired by another job, that depends on a pool, containing the same port and vice versa.

---
Originally reported by pepov, imported from: Port allocation from named dynamic pools

• assignee: pepov
  
• status: Open
  
• priority: Major
  
• component(s): port-allocator-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 20251216-225446
  

Raw content of original issue

In some cases, it is necessary for a job to aquire a port from a pool of predefined ports (eg. for using an independent memcache connection to be able to flush it on each test setup).


Each pool should have a name and an enumerated list of port numbers.


If a job depends on a pool, it is blocked until any of the pool's port gets released.


If a job has finished, it releases the aquired port, just as it is implemented with the fixed port allocation strategy.


Allocating a fixed port should lock that port from getting aquired by another job, that depends on a pool, containing the same port and vice versa.

1 attachment

- [port-allocator.patch](https://issues.jenkins.io/secure/attachment/20922/port-allocator.patch)