• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • None
    • Windows 10 pro version 1803,
      1.8.0_66-b18
      Jenkins 2.148

      Jenkins gives a notification that there is a new version (2.149).

      Click Upgrade Automatically. 

      Jenkins starts the download to jenkins.war twice, 

      and gives twice the blue ball and message 'installed' 

      There are at this time 3 files on disk: jenkins.war, jenkins.war.bak and jenkins.war.tmp

      Set 'restart' checkbox: only .war.bak remains after service is stopped.

      Jenkins fails to start because jenkins.war is not found.

       

      third attempt (while writing this report) succeeded.

      It only downloaded & installed once after setting 'udgrade automatically'.

      There are no other users on this serrver who will start an upgrade.

        1. DoubleClick.err
          2 kB
        2. Jenkins.err
          3 kB
        3. jenkins.xml
          2 kB

          [JENKINS-54318] Jenkins Upgrade Now deletes new .war at restart

          Daniel Beck added a comment -

          jamesivie To clarify, what version of Jenkins was running at the time you tried to upgrade? If it's older than 2.152, as per my previous comment, that's expected.

          Daniel Beck added a comment - jamesivie To clarify, what version of Jenkins was running at the time you tried to upgrade? If it's older than 2.152, as per my previous comment, that's expected.

          James added a comment - - edited

          I'm not sure that's clear at all, or what is happening or expected.  There was no double-clicking involved.  I clicked once to 'Upgrade Automatically' from 2.150 to 2.153.  Downloads appeared to finish.  I then clicked once to 'Restart', and Jenkins never came back up.  At this point, I have to manually restore the Jenkins.war file.  Are you saying that EVERYONE using 2.149-2.152 will have to go through a manual process to upgrade?

          James added a comment - - edited I'm not sure that's clear at all, or what is happening or expected.  There was no double-clicking involved.  I clicked once to 'Upgrade Automatically' from 2.150 to 2.153.  Downloads appeared to finish.  I then clicked once to 'Restart', and Jenkins never came back up.  At this point, I have to manually restore the Jenkins.war file.  Are you saying that EVERYONE using 2.149-2.152 will have to go through a manual process to upgrade?

          Daniel Beck added a comment -

          Are you saying that EVERYONE using 2.149-2.152 will have to go through a manual process to upgrade?

          If they use the built-in auto update, rather than a package manager, installer, or just replacing the docker image, I would expect so.

          Daniel Beck added a comment - Are you saying that EVERYONE using 2.149-2.152 will have to go through a manual process to upgrade? If they use the built-in auto update, rather than a package manager, installer, or just replacing the docker image, I would expect so.

          James added a comment -

          And what is the process to do a manual upgrade, exactly?  I'd rather not lose 50 build configs trying to update or be down for hours trying to figure out how to get back up.

          James added a comment - And what is the process to do a manual upgrade, exactly?  I'd rather not lose 50 build configs trying to update or be down for hours trying to figure out how to get back up.

          Daniel Beck added a comment -

          If jenkins.war.bak is the previously running version rather than the newly downloaded one, don't restore that, but instead download Jenkins from its website and place it where jenkins.war should be.

          Daniel Beck added a comment - If  jenkins.war.bak is the previously running version rather than the newly downloaded one, don't restore that, but instead download Jenkins from its website and place it where jenkins.war should be.

          James added a comment -

          Since I'm back up and running, I see there is a link to download the new WAR file, but I'm not sure people who are in the failed state will be able to find anything other than a full installation.  Any advice for them–they will probably eventually come here for help.  Also, is it OK to update just the WAR file by itself?  The Jenkins.exe (and who knows what else) won't match that version.

          James added a comment - Since I'm back up and running, I see there is a link to download the new WAR file, but I'm not sure people who are in the failed state will be able to find anything other than a full installation.  Any advice for them–they will probably eventually come here for help.  Also, is it OK to update just the WAR file by itself?  The Jenkins.exe (and who knows what else) won't match that version.

          Daniel Beck added a comment -

          If you've been using the Jenkins built-in update functionality, you've just replaced the war file all this time anyway.

          Daniel Beck added a comment - If you've been using the Jenkins built-in update functionality, you've just replaced the war file all this time anyway.

          James added a comment -

          For the rest of the planet whose Jenkins fails when they try to upgrade and their Jenkins.war file is missing, and who can't get to the link to the new WAR file to get back up and running because their Jenkins is down, here is the link to a new WAR file that will hopefully get you back up and running:

          http://updates.jenkins-ci.org/download/war/2.153/jenkins.war

          Put this file in your Jenkins folder (there should not be a file with the same name there already if you're in this state, but there should be a Jenkins.war.bak file that is the old version), and restart the service either through the UI, or using the CMD console and running "net start Jenkins".

          James added a comment - For the rest of the planet whose Jenkins fails when they try to upgrade and their Jenkins.war file is missing, and who can't get to the link to the new WAR file to get back up and running because their Jenkins is down, here is the link to a new WAR file that will hopefully get you back up and running: http://updates.jenkins-ci.org/download/war/2.153/jenkins.war Put this file in your Jenkins folder (there should  not be a file with the same name there already if you're in this state, but there should be a Jenkins.war.bak file that is the old version), and restart the service either through the UI, or using the CMD console and running "net start Jenkins".

          Last week I upgraded from 2.152 to 2.153 four times without trouble. 

           

          Because it has been an intermittent problem for me I reverted to 2.152 again and repeated the cycle a few times. 

          Also when trying to 'force' the issue with a doubleclick it worked fine. 

          Delayed feedback because I wanted to try the same on 2.154, but that's not out yet. 

           

          For me this issue can be marked as resolved.

          Rene Affourtit added a comment - Last week I upgraded from 2.152 to 2.153 four times without trouble.    Because it has been an intermittent problem for me I reverted to 2.152 again and repeated the cycle a few times.  Also when trying to 'force' the issue with a doubleclick it worked fine.  Delayed feedback because I wanted to try the same on 2.154, but that's not out yet.    For me this issue can be marked as resolved.

          Updated to 2.153 and 2.154.

          Both multiple times without any further issues.

          Rene Affourtit added a comment - Updated to 2.153 and 2.154. Both multiple times without any further issues.

            Unassigned Unassigned
            renea Rene Affourtit
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: