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

Consider removing the use of WinSW.NET2.exe

    XMLWordPrintable

Details

    • Jenkins 2.248

    Description

      The use of .exe.config file in Windows Slave Installer Module has prevented WinSW from running on machines without .NET FX 4+ installed since 2013. No one has reported that this is a problem in the past years. Instead, there are only issues regarding using .NET FX 2.0 executables on newer platforms.

      https://github.com/jenkinsci/windows-slave-installer-module/blob/windows-slave-installer-1.12/src/main/resources/org/jenkinsci/modules/windows_slave_installer/jenkins-slave.exe.config

      https://github.com/winsw/winsw/issues/399

      JENKINS-60005

      JENKINS-31564

      JENKINS-21484

      Therefore, I propose the following actions:

      • Safely switch to the .NET FX 4.0 executable in Windows Slave Installer Module.
      • Re-investigate the need to use .NET FX 2.0 executables in Jenkins master and slaves.

      Attachments

        Activity

          oleg_nenashev Oleg Nenashev added a comment -

          I agree this is something required. I will create a new EPIC for Windows Support updates and add this ticket there

          oleg_nenashev Oleg Nenashev added a comment - I agree this is something required. I will create a new EPIC for Windows Support updates and add this ticket there
          oleg_nenashev Oleg Nenashev added a comment -

          Released in Jenkins 2.248

          oleg_nenashev Oleg Nenashev added a comment - Released in Jenkins 2.248

          People

            oleg_nenashev Oleg Nenashev
            nextturn Next Turn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: