-
Bug
-
Resolution: Fixed
-
Minor
-
-
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"
- is duplicated by
-
JENKINS-68118 Debian Stretch upgraded Jenkins conflicts with Tomcat (http port error)
-
- Closed
-
- links to
[JENKINS-68007] Prefer --httpPort from JENKINS_ARGS over HTTP_PORT when the two differ
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Labels | New: lts-candidate |
Remote Link | New: This issue links to "jenkinsci/packaging#296 (Web Link)" [ 27481 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Fixed but Unreleased [ 10203 ] |
Released As | New: 2.339 | |
Status | Original: Fixed but Unreleased [ 10203 ] | New: Closed [ 6 ] |
Labels | Original: lts-candidate | New: 2.332.2-fixed |
Link |
New:
This issue is duplicated by |
Originally reported in jenkinsci/packaging#295, which has more context.