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.

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • packaging
    • Microsoft Windows slaves set to connect as a Windows service

    Description

      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.

      Attachments

        Issue Links

          Activity

            ricko 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.

            ricko 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.
            cobexer 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 =/.

            cobexer 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 =/.
            teilo 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.

            teilo 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.
            akit 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

            akit 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.

            cobexer 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.

            Fix on the way

            kohsuke Kohsuke Kawaguchi added a comment - Fix on the way

            Code changed in jenkins
            User: Kohsuke Kawaguchi
            Path:
            core/src/main/resources/windows-service/jenkins.exe.config
            http://jenkins-ci.org/commit/jenkins/b08d7c7ee7e7ff589dcc5e5bdd40a014b0213a65
            Log:
            [FIXED JENKINS-21484]

            Don't require ancient .NET 2.0 runtime. .NET 4.0 can host this
            executable, too.

            See https://github.com/kohsuke/winsw#net-runtime-40

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/resources/windows-service/jenkins.exe.config http://jenkins-ci.org/commit/jenkins/b08d7c7ee7e7ff589dcc5e5bdd40a014b0213a65 Log: [FIXED JENKINS-21484] Don't require ancient .NET 2.0 runtime. .NET 4.0 can host this executable, too. See https://github.com/kohsuke/winsw#net-runtime-40

            Code changed in jenkins
            User: Kohsuke Kawaguchi
            Path:
            core/src/main/resources/windows-service/jenkins.exe.config
            http://jenkins-ci.org/commit/jenkins/9fce1ee933eb5276baff977d562fc8e183f1c8d6
            Log:
            Merge pull request #2124 from kohsuke/jenkins-21484

            [FIXED JENKINS-21484]

            Compare: https://github.com/jenkinsci/jenkins/compare/5a6c1ebb03b1...9fce1ee933eb

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/resources/windows-service/jenkins.exe.config http://jenkins-ci.org/commit/jenkins/9fce1ee933eb5276baff977d562fc8e183f1c8d6 Log: Merge pull request #2124 from kohsuke/jenkins-21484 [FIXED JENKINS-21484] Compare: https://github.com/jenkinsci/jenkins/compare/5a6c1ebb03b1...9fce1ee933eb
            dogfood dogfood added a comment -

            Integrated in jenkins_main_trunk #4506
            [FIXED JENKINS-21484] (Revision b08d7c7ee7e7ff589dcc5e5bdd40a014b0213a65)

            Result = UNSTABLE
            kohsuke : b08d7c7ee7e7ff589dcc5e5bdd40a014b0213a65
            Files :

            • core/src/main/resources/windows-service/jenkins.exe.config
            dogfood dogfood added a comment - Integrated in jenkins_main_trunk #4506 [FIXED JENKINS-21484] (Revision b08d7c7ee7e7ff589dcc5e5bdd40a014b0213a65) Result = UNSTABLE kohsuke : b08d7c7ee7e7ff589dcc5e5bdd40a014b0213a65 Files : core/src/main/resources/windows-service/jenkins.exe.config

            People

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

              Dates

                Created:
                Updated:
                Resolved: