-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Platform: All, OS: All
Steps to reproduce :
1. Selected "Allow Unique TCP port allocation"
2. Created Hudson variables for TCP ports
3. Used Hudson variables in execution script
4. Ports are dynamically assigned by Hudson.
5. Still getting port conflict in some runs .
Seems to be an intermittent issue but it is still affecting the builds .
- is related to
-
JENKINS-19093 pooled ports not assigned uniquely across maxes of multiconf projects
-
- Resolved
-
I've noticed this for some of my jobs that utilize Fitnesse and it appears to be because part of fitnesse is actually allocating a range of ports starting from the port number passed in (the SLIM Server subsystem). Is there a way we could add a port range option and allocate a random port and 'n' port beyond that?