-
Bug
-
Resolution: Not A Defect
-
Critical
-
None
-
Jenkins LTS on Linux, Plugin version 1.8
As the general port range is not customizable and also uses ports from the ephemeral port range I had to create a port pool to get ports in an acceptable range. Now using this pool in multiconf project results in port conflicts, as all axes of a multiconf project receive the same port from the pool instead of different ones. This should be avoided as it renders the plugin useless for us.
- is related to
-
JENKINS-2723 Port conflict despite unique port assignment
-
- Open
-
[JENKINS-19093] pooled ports not assigned uniquely across maxes of multiconf projects
Link | New: This issue is related to JENKINS-2723 [ JENKINS-2723 ] |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 150540 ] | New: JNJira + In-Review [ 193575 ] |