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

2.332.1 upgrade changes JENKINS_WAR default location but doesn't apply it in the configuration

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • 2.332.1 (from 2.319.1)
      Red Hat Enterprise Linux release 8.5
    • 2.332.2

      We upgraded from 2.319.1 to 2.332.1 and I noticed that the WAR file was moved from /usr/lib/jenkins/jenkins.war to /usr/share/java/jenkins.war.

      In the new configuration file (override.conf), it still points to /usr/lib/jenkins/jenkins.war.

       

      Either the migration script should take this into account or a note should be posted that there is a new default WAR location

       

          [JENKINS-68149] 2.332.1 upgrade changes JENKINS_WAR default location but doesn't apply it in the configuration

          Jan created issue -
          Basil Crow made changes -
          Assignee New: Basil Crow [ basil ]
          Basil Crow made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Basil Crow made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Basil Crow made changes -
          Remote Link New: This issue links to "jenkinsci/packaging#301 (Web Link)" [ 27518 ]
          Mark Waite made changes -
          Comment [ Can you provide more details based on the ["Reporting Issues"|https://www.jenkins.io/blog/2022/03/25/systemd-migration/#reporting-issues] in the [blog post|https://www.jenkins.io/blog/2022/03/25/systemd-migration/]?

          # Provide the contents of the old System V init(8) configuration in /etc/sysconfig/jenkins, sanitized as necessary.
          # Provide the contents of the systemd(1) drop-in unit in /etc/systemd/system/jenkins.service.d/override.conf, sanitized as necessary.
          # Provide steps to reproduce the issue from scratch on a minimal Jenkins installation; the scenario should fail when the steps are followed on Jenkins 2.335 or later and pass when the steps are followed on Jenkins 2.334 or earlier

          My RHEL 8 installation did not have that behavior. We'll need to understand what was different between your installation and others.
          ]
          Mark Waite made changes -
          Labels New: lts-candidate
          Mark Waite made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Fixed but Unreleased [ 10203 ]
          Ildefonso Montero made changes -
          Released As New: 2.332.2
          Status Original: Fixed but Unreleased [ 10203 ] New: Resolved [ 5 ]
          Alexander Brandes made changes -
          Labels Original: lts-candidate New: 2.332.3-fixed lts-candidate

            basil Basil Crow
            meiswjn Jan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: