jenkinsci / jenkinsci/port-allocator-plugin
[JENKINS-6647] Add ability to allocate range of TCP Ports
- Dominant language
- Java
- Stars
- 11
- Forks
- 34
- Avg merge
- 23h 26m
- Merged PRs (30d)
- 1
Description
It would be nice to be able to ask for a range of ports (not necessarily contiguous, but that could be a useful option I suppose) given a name, the variables would be allocated with a counter suffix.
For instance, I'm thinking of two fields being presented: "Name" and "Count". If the user eneted, "Foo", and "10", then Foo1, Foo2, Foo3 ... Foo10 would all be allocated.
---
Originally reported by
esmalling, imported from: Add ability to allocate range of TCP Ports
Raw content of original issue
It would be nice to be able to ask for a range of ports (not necessarily contiguous, but that could be a useful option I suppose) given a name, the variables would be allocated with a counter suffix.
For instance, I'm thinking of two fields being presented: "Name" and "Count". If the user eneted, "Foo", and "10", then Foo1, Foo2, Foo3 ... Foo10 would all be allocated.
Contributor guide
Research direction
Start by reviewing the port-allocator-plugin's existing port allocation behavior and how allocation inputs are represented. Clarify whether ranges must be contiguous, how names and counters are exposed, and how conflicts or partial allocation are handled. Done should include agreed behavior, implementation coverage, and tests for requesting multiple ports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100