Prefer --httpPort from JENKINS_ARGS over HTTP_PORT when the two differ

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

XMLWordPrintable

    • 2.339, 2.332.2

      Steps to reproduce

      On Debian, migrate from an installation with

      HTTP_PORT=9999 # Garbage, only used by old Debian system V init script to check if the port was in use, not to actually start Jenkins
JENKINS_ARGS="--webroot=/var/cache/$NAME/war --httpPort=8081" # The --httpPort argument is used to actually start Jenkins

      Expected results

      Note: These are the actual results when migrating from an installation with

      HTTP_PORT=8081
JENKINS_ARGS="--webroot=/var/cache/$NAME/war --httpPort=$HTTP_PORT"

      (which is the canonical example that we ship).

      The override.conf contains

      [Service]
Environment="JENKINS_PORT=8081"

      Actual results

      The override.conf contains

      [Service]
Environment="JENKINS_PORT=9999"

            Assignee:
            Basil Crow
            Reporter:
            Basil Crow
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: