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

Inconsistent versions in update error message

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Trivial Trivial
    • core
    • None
    • 2.122 on OpenJDK 1.8.0_151-b12, Linux

      Noticed a minor (and very unimportant) glitch as a result of JENKINS-51447.

      After previously failing to download 2.123, and then manually triggering an update check, the error popup now reads "Upgrade to Jenkins 2.124 failed: Failed to download from http://updates.jenkins-ci.org/download/war/2.123/jenkins.war (redirected to: http://mirrors.jenkins-ci.org/war/2.123/jenkins.war)." (Note the version mismatch between the message and the URL - they matched before the 2.124 update was detected).

      Triggering the retry correctly downloads the newly released 2.124.

      (The above was starting from an existing 2.122 installation).

          [JENKINS-51461] Inconsistent versions in update error message

          Oleg Nenashev added a comment -

          2.123 release has been corrupted due to the release flow issue, see JENKINS-51447.
          Now it is fixed in the out-of-order 2.124 release, so it should not impact users anymore.

          Oleg Nenashev added a comment - 2.123 release has been corrupted due to the release flow issue, see JENKINS-51447 . Now it is fixed in the out-of-order 2.124 release, so it should not impact users anymore.

          Paul Milliken added a comment -

          I do not believe that this is specific to the issues with the 2.123 release. It appears that the error popup is built from data which is not necessarily in sync - the error from the previous update attempt, and the currently available update version, as opposed to the version which was available when the attempt was made.

          I agree that this is very unlikely to occur in general, however, it would make sense if the error reliably indicated which version upgrade was actually attempted.

          Paul Milliken added a comment - I do not believe that this is specific to the issues with the 2.123 release. It appears that the error popup is built from data which is not necessarily in sync - the error from the previous update attempt, and the  currently available update version, as opposed to the version which was available when the attempt was made. I agree that this is very unlikely to occur in general, however, it would make sense if the error reliably indicated which version upgrade was actually attempted.

          Oleg Nenashev added a comment -

          Agreed. Reopening it

          Oleg Nenashev added a comment - Agreed. Reopening it

            Unassigned Unassigned
            pmilliken Paul Milliken
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: