Port allocation duplicate on "Concurrent builds"

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: port-allocator-plugin
    • Environment:
      Jenkins Version: 2.5
      OS: Ubuntu
      Guess it is introduced in Jenkins 2.0?
      Was there a rewrite in how plugins are loaded when running concurrent? Its own classloader?

      When configuring a "Pooled TCP port", the pool assignment is not unique when the build is performed concurrently (see "Execute concurrent builds if necessary").

      Never had an issue before and problem seems to be introduced after we updated to Jenkins 2.0.

      Easy repro:

      • create new job with "Pooled TCP port" and "Execute concurrent builds if necessary" options
      • execute build multiple times
      • see console output: same port is assigned multiple times

            Assignee:
            Andres Rodriguez
            Reporter:
            Rick Oosterholt
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: