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

Jenkins Windows slave service exe requires .NET 2.0 only. Allow it to work with later .NET versions.

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • packaging
    • Microsoft Windows slaves set to connect as a Windows service

      Recent Windows Server OS's come with .NET 4 pre-installed.
      The Jenkins slave Windows service exe requires .NET 2.0 only and will not run with .NET 4.0 or later.
      This should be a simple configuration change in the build of the Windows exe assembly.

          [JENKINS-21484] Jenkins Windows slave service exe requires .NET 2.0 only. Allow it to work with later .NET versions.

          Richard Otter created issue -

          Richard Otter added a comment -

          The point of this improvement request is to make creation of a Windows node easier.
          There is a list of about 20 steps that need to happen before Jenkins and Windows are happy together. Making this simple improvement will eliminate 2 of them.

          Using the current Jenkins build, trying to connect to a node which does not have the old version of .NET shows a connection log that just hangs on "starting service". Trouble shooting is not straightforward for the novice Jenkins user.

          Richard Otter added a comment - The point of this improvement request is to make creation of a Windows node easier. There is a list of about 20 steps that need to happen before Jenkins and Windows are happy together. Making this simple improvement will eliminate 2 of them. Using the current Jenkins build, trying to connect to a node which does not have the old version of .NET shows a connection log that just hangs on "starting service". Trouble shooting is not straightforward for the novice Jenkins user.
          Ing. Christoph Obexer made changes -
          Labels New: 2.0

          Ing. Christoph Obexer added a comment - - edited

          Windows 10 doesn't come with .NET 3.5. it's really annoying that I have to install an old .NET version to enable use as a Jenkins slave.
          The installation of .NET on Windows 10 requires quite a few manual steps if the VM doesn't have Internet access =/.

          Ing. Christoph Obexer added a comment - - edited Windows 10 doesn't come with .NET 3.5. it's really annoying that I have to install an old .NET version to enable use as a Jenkins slave. The installation of .NET on Windows 10 requires quite a few manual steps if the VM doesn't have Internet access =/.

          James Nord added a comment - - edited

          The installation of .NET on Windows 10 requires quite a few manual steps if the VM doesn't have Internet access

          cobexer you should just need the installation media for windows 10 as it is still a core windows feature.

          James Nord added a comment - - edited The installation of .NET on Windows 10 requires quite a few manual steps if the VM doesn't have Internet access cobexer you should just need the installation media for windows 10 as it is still a core windows feature.

          You Me added a comment -

          Hi,
          I need some help and I wasn't where to put my question for assistant.

          Issue: Jenkins is going through the proxy even though I setup the No Host proxy.
          Jenkins version 1.554.3 ,
          JDk 6
          To integrage Jenkins with Sonatype Nexus CLM
          Sonatype CLM for CI Plugin 2.14.2-01

          You Me added a comment - Hi, I need some help and I wasn't where to put my question for assistant. Issue: Jenkins is going through the proxy even though I setup the No Host proxy. Jenkins version 1.554.3 , JDk 6 To integrage Jenkins with Sonatype Nexus CLM Sonatype CLM for CI Plugin 2.14.2-01

          Yes you need the installation media back in the virtual DVD drive (aka going back to the hyper-visor management, hunting down the DVD, switching it in) and the you need to Google the dism command to manually install because the normal ways won't actually find the .NET sources,...
          But in the end Microsoft wants to see .NET 2.0 die, and newer .net version are available by default and updating the code should be easy? (no?)

          This is simply an UX defect in that it requires more work and makes Jenkins look bad because it requires an ancient version of .NET.

          Ing. Christoph Obexer added a comment - Yes you need the installation media back in the virtual DVD drive (aka going back to the hyper-visor management, hunting down the DVD, switching it in) and the you need to Google the dism command to manually install because the normal ways won't actually find the .NET sources,... But in the end Microsoft wants to see .NET 2.0 die, and newer .net version are available by default and updating the code should be easy? (no?) This is simply an UX defect in that it requires more work and makes Jenkins look bad because it requires an ancient version of .NET.
          You Me made changes -
          Assignee Original: Kohsuke Kawaguchi [ kohsuke ] New: You Me [ akit ]
          You Me made changes -
          Assignee Original: You Me [ akit ]
          Kohsuke Kawaguchi made changes -
          Component/s New: packaging [ 20120 ]
          Component/s Original: windows-slaves-plugin [ 18327 ]

            Unassigned Unassigned
            ricko Richard Otter
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: