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

Windows DisplayVersion registry value has not been updated after installing the newest version

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • packaging
    • None
    • Windows Server

      Hi
      I have upgraded our Jenkins installed on Windows Server to the newest version and I found out that the DisplayVersion in registry is: 2.255.2772, DiplayName: 2.277.2
      It make us a lot of isseus with our CrowdStrike beacuse it thinks that Jenkins is not up to date and it send us a lot of alerts.
      Can anyone fix it?
      Our installed version is: 2.401.1 

          [JENKINS-71372] Windows DisplayVersion registry value has not been updated after installing the newest version

          Mark Waite added a comment -

          As far as I understand it, the recommended way to upgrade the Jenkins controller on Windows does not update the version number stored in the Windows registry. The Crowdstrike report is checking the wrong values if it is claiming that Jenkins is out of date.

          Mark Waite added a comment - As far as I understand it, the recommended way to upgrade the Jenkins controller on Windows does not update the version number stored in the Windows registry. The Crowdstrike report is checking the wrong values if it is claiming that Jenkins is out of date.

          Alex Earl added a comment - - edited

          FYI, I am looking at providing a script that can be run after the upgrade on the system to update the registry information for Jenkins from the upgraded war file. I don't think we can do this automatically, but I will look into that as a future enhancement.

           

          Crowdstrike is probably looking at the registry values for the version, which is not updated when you upgrade the war using the Jenkins UI.

          Alex Earl added a comment - - edited FYI, I am looking at providing a script that can be run after the upgrade on the system to update the registry information for Jenkins from the upgraded war file. I don't think we can do this automatically, but I will look into that as a future enhancement.   Crowdstrike is probably looking at the registry values for the version, which is not updated when you upgrade the war using the Jenkins UI.

            slide_o_mix Alex Earl
            djwheele Marcin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: