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

Default Jenkins %JENKINS_HOME% to be Windows compliant on Windows machines

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      2.235.3

      Description

      When Jenkins installs on Windows machines, it doesn't store customer/program configuration in Microsoft defined system wide directories appropriate for this purpose. Instead it reconfigures its program folder to unsolicitedly store customer/program configuration in there.

      Not only is the current approach unsafe, because the Jenkins installer grants Write access rights to a folder containing executables. In addition, when system administrators are required to create a backup plan, they usually set-up their backup software to look in CommonApplicationData (usually "C:\ProgramData\") for program specific custom files and in ApplicationData (usually "C:\Users\<LoginName>\AppData\Roaming\") for user specific program custom files on all their machines.

      ... And wait, oh, yes, if Jenkins may be installed on any of those machines, they also need to amend their backup set-up for this particular machine to also look in the "C:\Program Files (x86)\Jenkins\" folder, because its software develpers gave a damn about operating system guidelines.

      Given the critical ramifications of the current Jenkins setup, please amend the Jenkins installer to properly set CommonApplicationData and ApplicationData, resp, for "%JENKINS_HOME%".

       

      Here are two links to a list of Microsoft Windows' special folders:

      https://msdn.microsoft.com/en-us/library/system.environment.specialfolder(v=vs.110).aspx

      https://docs.microsoft.com/en-us/windows/desktop/shell/knownfolderid

       

        Attachments

          Activity

          settrend A. D. created issue -
          settrend A. D. made changes -
          Field Original Value New Value
          Description When Jenkins installs on Windows machines, it doesn't store customer/program configuration in Microsoft defined system wide directories appropriate for this purpose. Instead it reconfigures its program folder to unsolicitedly store customer/program configuration in there.

          Not only is the current approach unsafe, because the Jenkins installer grants Write access rights to a folder containing executables. In addition, when system administrators are required to create a backup plan, they usually set-up their backup software to look in *CommonApplicationData* (usually "C:\ProgramData\") for program specific custom files and in *ApplicationData* (usually "C:\Users\\{LoginName}\AppData\Roaming\") on all their machines.

          ... And wait, oh, yes, if *Jenkins* may be installed on any of those machines, they also need to amend their backup set-up for this particular machine to also look in the "C:\Program Files (x86)\Jenkins\" folder, because its software develpers gave a damn about operating system guidelines.

          Thus, please amend the Jenkins installer to properly set *CommonApplicationData* and *ApplicationData*, resp, for "%JENKINS_HOME%".

           

          Here are two links to a list of Microsoft Windows' special folders:

          [https://msdn.microsoft.com/en-us/library/system.environment.specialfolder(v=vs.110).aspx]

          [https://docs.microsoft.com/de-de/windows/desktop/shell/knownfolderid]

           
          When Jenkins installs on Windows machines, it doesn't store customer/program configuration in Microsoft defined system wide directories appropriate for this purpose. Instead it reconfigures its program folder to unsolicitedly store customer/program configuration in there.

          Not only is the current approach unsafe, because the Jenkins installer grants Write access rights to a folder containing executables. In addition, when system administrators are required to create a backup plan, they usually set-up their backup software to look in *CommonApplicationData* (usually "C:\ProgramData\") for program specific custom files and in *ApplicationData* (usually "C:\Users\<LoginName>\AppData\Roaming\") on all their machines.

          ... And wait, oh, yes, if *Jenkins* may be installed on any of those machines, they also need to amend their backup set-up for this particular machine to also look in the "C:\Program Files (x86)\Jenkins\" folder, because its software develpers gave a damn about operating system guidelines.

          Thus, please amend the Jenkins installer to properly set *CommonApplicationData* and *ApplicationData*, resp, for "%JENKINS_HOME%".

           

          Here are two links to a list of Microsoft Windows' special folders:

          [https://msdn.microsoft.com/en-us/library/system.environment.specialfolder(v=vs.110).aspx]

          [https://docs.microsoft.com/de-de/windows/desktop/shell/knownfolderid]

           
          settrend A. D. made changes -
          Description When Jenkins installs on Windows machines, it doesn't store customer/program configuration in Microsoft defined system wide directories appropriate for this purpose. Instead it reconfigures its program folder to unsolicitedly store customer/program configuration in there.

          Not only is the current approach unsafe, because the Jenkins installer grants Write access rights to a folder containing executables. In addition, when system administrators are required to create a backup plan, they usually set-up their backup software to look in *CommonApplicationData* (usually "C:\ProgramData\") for program specific custom files and in *ApplicationData* (usually "C:\Users\<LoginName>\AppData\Roaming\") on all their machines.

          ... And wait, oh, yes, if *Jenkins* may be installed on any of those machines, they also need to amend their backup set-up for this particular machine to also look in the "C:\Program Files (x86)\Jenkins\" folder, because its software develpers gave a damn about operating system guidelines.

          Thus, please amend the Jenkins installer to properly set *CommonApplicationData* and *ApplicationData*, resp, for "%JENKINS_HOME%".

           

          Here are two links to a list of Microsoft Windows' special folders:

          [https://msdn.microsoft.com/en-us/library/system.environment.specialfolder(v=vs.110).aspx]

          [https://docs.microsoft.com/de-de/windows/desktop/shell/knownfolderid]

           
          When Jenkins installs on Windows machines, it doesn't store customer/program configuration in Microsoft defined system wide directories appropriate for this purpose. Instead it reconfigures its program folder to unsolicitedly store customer/program configuration in there.

          Not only is the current approach unsafe, because the Jenkins installer grants Write access rights to a folder containing executables. In addition, when system administrators are required to create a backup plan, they usually set-up their backup software to look in *CommonApplicationData* (usually "C:\ProgramData\") for program specific custom files and in *ApplicationData* (usually "C:\Users\<LoginName>\AppData\Roaming\") for user specific program custom files on all their machines.

          ... And wait, oh, yes, if *Jenkins* may be installed on any of those machines, they also need to amend their backup set-up for this particular machine to also look in the "C:\Program Files (x86)\Jenkins\" folder, because its software develpers gave a damn about operating system guidelines.

          Thus, please amend the Jenkins installer to properly set *CommonApplicationData* and *ApplicationData*, resp, for "%JENKINS_HOME%".

           

          Here are two links to a list of Microsoft Windows' special folders:

          [https://msdn.microsoft.com/en-us/library/system.environment.specialfolder(v=vs.110).aspx]

          [https://docs.microsoft.com/de-de/windows/desktop/shell/knownfolderid]

           
          settrend A. D. made changes -
          Description When Jenkins installs on Windows machines, it doesn't store customer/program configuration in Microsoft defined system wide directories appropriate for this purpose. Instead it reconfigures its program folder to unsolicitedly store customer/program configuration in there.

          Not only is the current approach unsafe, because the Jenkins installer grants Write access rights to a folder containing executables. In addition, when system administrators are required to create a backup plan, they usually set-up their backup software to look in *CommonApplicationData* (usually "C:\ProgramData\") for program specific custom files and in *ApplicationData* (usually "C:\Users\<LoginName>\AppData\Roaming\") for user specific program custom files on all their machines.

          ... And wait, oh, yes, if *Jenkins* may be installed on any of those machines, they also need to amend their backup set-up for this particular machine to also look in the "C:\Program Files (x86)\Jenkins\" folder, because its software develpers gave a damn about operating system guidelines.

          Thus, please amend the Jenkins installer to properly set *CommonApplicationData* and *ApplicationData*, resp, for "%JENKINS_HOME%".

           

          Here are two links to a list of Microsoft Windows' special folders:

          [https://msdn.microsoft.com/en-us/library/system.environment.specialfolder(v=vs.110).aspx]

          [https://docs.microsoft.com/de-de/windows/desktop/shell/knownfolderid]

           
          When Jenkins installs on Windows machines, it doesn't store customer/program configuration in Microsoft defined system wide directories appropriate for this purpose. Instead it reconfigures its program folder to unsolicitedly store customer/program configuration in there.

          Not only is the current approach unsafe, because the Jenkins installer grants Write access rights to a folder containing executables. In addition, when system administrators are required to create a backup plan, they usually set-up their backup software to look in *CommonApplicationData* (usually "C:\ProgramData\") for program specific custom files and in *ApplicationData* (usually "C:\Users\<LoginName>\AppData\Roaming\") for user specific program custom files on all their machines.

          ... And wait, oh, yes, if *Jenkins* may be installed on any of those machines, they also need to amend their backup set-up for this particular machine to also look in the "C:\Program Files (x86)\Jenkins\" folder, because its software develpers gave a damn about operating system guidelines.

          Given the critical ramifications of the current Jenkins setup, please amend the Jenkins installer to properly set *CommonApplicationData* and *ApplicationData*, resp, for "%JENKINS_HOME%".

           

          Here are two links to a list of Microsoft Windows' special folders:

          [https://msdn.microsoft.com/en-us/library/system.environment.specialfolder(v=vs.110).aspx]

          [https://docs.microsoft.com/de-de/windows/desktop/shell/knownfolderid]

           
          settrend A. D. made changes -
          Description When Jenkins installs on Windows machines, it doesn't store customer/program configuration in Microsoft defined system wide directories appropriate for this purpose. Instead it reconfigures its program folder to unsolicitedly store customer/program configuration in there.

          Not only is the current approach unsafe, because the Jenkins installer grants Write access rights to a folder containing executables. In addition, when system administrators are required to create a backup plan, they usually set-up their backup software to look in *CommonApplicationData* (usually "C:\ProgramData\") for program specific custom files and in *ApplicationData* (usually "C:\Users\<LoginName>\AppData\Roaming\") for user specific program custom files on all their machines.

          ... And wait, oh, yes, if *Jenkins* may be installed on any of those machines, they also need to amend their backup set-up for this particular machine to also look in the "C:\Program Files (x86)\Jenkins\" folder, because its software develpers gave a damn about operating system guidelines.

          Given the critical ramifications of the current Jenkins setup, please amend the Jenkins installer to properly set *CommonApplicationData* and *ApplicationData*, resp, for "%JENKINS_HOME%".

           

          Here are two links to a list of Microsoft Windows' special folders:

          [https://msdn.microsoft.com/en-us/library/system.environment.specialfolder(v=vs.110).aspx]

          [https://docs.microsoft.com/de-de/windows/desktop/shell/knownfolderid]

           
          When Jenkins installs on Windows machines, it doesn't store customer/program configuration in Microsoft defined system wide directories appropriate for this purpose. Instead it reconfigures its program folder to unsolicitedly store customer/program configuration in there.

          Not only is the current approach unsafe, because the Jenkins installer grants Write access rights to a folder containing executables. In addition, when system administrators are required to create a backup plan, they usually set-up their backup software to look in *CommonApplicationData* (usually "C:\ProgramData\") for program specific custom files and in *ApplicationData* (usually "C:\Users\<LoginName>\AppData\Roaming\") for user specific program custom files on all their machines.

          ... And wait, oh, yes, if *Jenkins* may be installed on any of those machines, they also need to amend their backup set-up for this particular machine to also look in the "C:\Program Files (x86)\Jenkins\" folder, because its software develpers gave a damn about operating system guidelines.

          Given the critical ramifications of the current Jenkins setup, please amend the Jenkins installer to properly set *CommonApplicationData* and *ApplicationData*, resp, for "%JENKINS_HOME%".

           

          Here are two links to a list of Microsoft Windows' special folders:

          [https://msdn.microsoft.com/en-us/library/system.environment.specialfolder(v=vs.110).aspx]

          [https://docs.microsoft.com/en-us/windows/desktop/shell/knownfolderid|https://docs.microsoft.com/de-de/windows/desktop/shell/knownfolderid]

           
          oleg_nenashev Oleg Nenashev made changes -
          Component/s packaging [ 20120 ]
          Component/s core [ 15593 ]
          oleg_nenashev Oleg Nenashev made changes -
          Labels installer windows
          Hide
          kon Kalle Niemitalo added a comment -

          According to Windows Installer Upgrades, JENKINS_HOME was moved into LocalAppData in the 2.235.3 installer. See the property assignment in jenkins.wxs.

          Show
          kon Kalle Niemitalo added a comment - According to Windows Installer Upgrades , JENKINS_HOME was moved into LocalAppData in the 2.235.3 installer. See the property assignment in jenkins.wxs .
          kon Kalle Niemitalo made changes -
          Released As 2.235.3
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          markewaite Mark Waite made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            settrend A. D.
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: