Minor The guide how to install a Windows agent is really old, so it needs an update:
- JLNP is not supported anymore in Java 11, so the guide is missing an hint, how to install an agent on a Windows machine
- When you select New Node and don't want that the master stores any credential of the client (so you don't want SSHLauncher or CommandLauncher) you have only the remaining options JNLPLauncher and ManagedWindowsServiceLauncher. First one requires Java 8 or below, during it doesn't support Java 11, and the ManagedWindowsServiceLauncher option recommends to use the JNLPLauncher.
- Even when you know there exists a Windows Agent Installer module for Jenkins you have no idea how to install an agent with Java 11, as the automatic installation says you should start the agent via JNLP agents.
So in general it seems there is currently no official guide how to install an agent on a Windows machine.
[JENKINS-63237] Update guide for the installation of a Windows agent
sunblack
created issue -
| Summary | Original: Update guide for the installation of a Windows Slave | New: Update guide for the installation of a Windows agent |
| Description |
Original:
The [guide|https://wiki.jenkins.io/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice(require.NET2.0framework)] how to install a Windows slave is really old, so it needs an update: * JLNP is not supported anymore in Java 11, so the guide is missing an hint, how to install a slave on a Windows machine * When you select {{New Node}} and don't want that the master stores any credential of the client (so you don't want {{SSHLauncher}} or {{CommandLauncher}}) you have only the remaining options {{JNLPLauncher}} and {{ManagedWindowsServiceLauncher}}. First one requires Java 8 or below, during it doesn't support Java 11, and the {{ManagedWindowsServiceLauncher}} option recommends to use the {{JNLPLauncher}}. * Even when you know there exists a [Windows Agent Installer module for Jenkins|https://github.com/jenkinsci/windows-slave-installer-module] you have no idea how to install a slave with Java 11, as the automatic installation says you should start the slave via JNLP agents. So in general it seems there is currently no official guide how to install a slave on a Windows machine. |
New:
The [guide|https://wiki.jenkins.io/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice(require.NET2.0framework)] how to install a Windows agent is really old, so it needs an update: * JLNP is not supported anymore in Java 11, so the guide is missing an hint, how to install an agent on a Windows machine * When you select {{New Node}} and don't want that the master stores any credential of the client (so you don't want {{SSHLauncher}} or {{CommandLauncher}}) you have only the remaining options {{JNLPLauncher}} and {{ManagedWindowsServiceLauncher}}. First one requires Java 8 or below, during it doesn't support Java 11, and the {{ManagedWindowsServiceLauncher}} option recommends to use the {{JNLPLauncher}}. * Even when you know there exists a [Windows Agent Installer module for Jenkins|https://github.com/jenkinsci/windows-slave-installer-module] you have no idea how to install an agent with Java 11, as the automatic installation says you should start the agent via JNLP agents. So in general it seems there is currently no official guide how to install an agent on a Windows machine. |
https://github.com/jenkins-infra/jenkins.io/issues/3198 is a task for this update on jenkins.io. sunblack if you are interested to contribute, it would be much appreciated
| Remote Link | New: This issue links to "https://github.com/jenkins-infra/jenkins.io/issues/3198 (Web Link)" [ 25401 ] |
I believe some entries have been already migrated to jenkins.io. But yes, we need to facelift the guidelines