-
Improvement
-
Resolution: Fixed
-
Minor
-
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.
- is related to
-
JENKINS-31564 Windows Slave service cannot be installed on Windows Service 2012 R2 due to the missing .NET3.5
-
- Closed
-
- links to
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.