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

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

    XMLWordPrintable

Details

    • 2.339, 2.332.2

    Description

      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"

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-68118 Debian Stretch upgraded Jenkins conflicts with Tomcat (http port error)

          • Major - Major loss of function.
          • Closed
          links to

          Web Link jenkinsci/packaging#296

          Activity

            People

              basil Basil Crow
              basil Basil Crow
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: