Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-19093

pooled ports not assigned uniquely across maxes of multiconf projects

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Critical Critical
    • port-allocator-plugin
    • 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.

          [JENKINS-19093] pooled ports not assigned uniquely across maxes of multiconf projects

          Johannes Wienke added a comment - - edited

          Added the relation to JENKINS-2723 because this is partially the reason why I had to use pools.

          Johannes Wienke added a comment - - edited Added the relation to JENKINS-2723 because this is partially the reason why I had to use pools.

          Sorry, seems to be invalid. Our problem was caused by jobs actually allocating more tan one port and hence there were still conflicts inside the pool.

          Johannes Wienke added a comment - Sorry, seems to be invalid. Our problem was caused by jobs actually allocating more tan one port and hence there were still conflicts inside the pool.

            ramapulavarthi ramapulavarthi
            languitar Johannes Wienke
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: