Uploaded image for project: 'Jenkins Website'
  1. Jenkins Website
  2. WEBSITE-758

Most recent version is not installed

    XMLWordPrintable

Details

    • Bug
    • Status: Done (View Workflow)
    • Minor
    • Resolution: Fixed
    • content
    • None

    Description

      Clicking on the link to Download Jenkins 2.241 for Windows (https://www.jenkins.io/download/thank-you-downloading-windows-installer) installs Jenkins 2.233 instead of 2.241

      Attachments

        Activity

          markewaite Mark Waite added a comment -

          Thanks for reporting it! The Windows installer build process was broken by some Microsoft security changes that affected our infrastructure. The necessary changes have been applied so that the Jenkins 2.242 installer is now available for Windows. However, the jenkins.io downloads page has not yet been updated to point to the current Windows installer.

          We'll track that fix for the jenkins.io site in https://github.com/jenkins-infra/jenkins.io/issues/3476

          markewaite Mark Waite added a comment - Thanks for reporting it! The Windows installer build process was broken by some Microsoft security changes that affected our infrastructure. The necessary changes have been applied so that the Jenkins 2.242 installer is now available for Windows. However, the jenkins.io downloads page has not yet been updated to point to the current Windows installer. We'll track that fix for the jenkins.io site in https://github.com/jenkins-infra/jenkins.io/issues/3476
          markewaite Mark Waite added a comment -

          First pull request needs to be merged and run in a weekly build before the symlink will be correct.

          We could run a temporary job on release.ci.jenkins.io that only updates the symlink. The code fragment that updates the symlink is small but the execution context (credentials, etc.) is large and easy to make a mistake when creating a temporary environment.

          markewaite Mark Waite added a comment - First pull request needs to be merged and run in a weekly build before the symlink will be correct. We could run a temporary job on release.ci.jenkins.io that only updates the symlink. The code fragment that updates the symlink is small but the execution context (credentials, etc.) is large and easy to make a mistake when creating a temporary environment.
          markewaite Mark Waite added a comment -

          Resolved with Jenkins weekly 2.243. Thanks for reporting it.

          markewaite Mark Waite added a comment - Resolved with Jenkins weekly 2.243. Thanks for reporting it.

          People

            markewaite Mark Waite
            bstlwstl Sebastian
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: