-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Windows Server 2008 R2
I set a server address in the Tunnel connection through field for Launch slave agents via Java Web Start but that was not represented in the JNLP file which had no tunnel parameter. This does work as expected when creating the slave via the regular Jenkins slave configuration but not the one in vSphere-cloud.
[JENKINS-22827] Parameters entered into the "Tunnel connection through" section of "Launch slave agents via Java Web Start" are not writen into the JNLP file
I ran into this problem yesterday while trying to setup a slave the Web Start service on Windows. The workaround I used was to download the JNLP file with curl, and slave.jar, both to the folder defined in 'Remote FS root'. In my case that's C:\Jenkins. I edited the JNLP file, manually adding the tunnel arguments, then I creates a batch file with the following:
java -jar slave.jar -noCertificateCheck -jnlpUrl file:///C:/Jenkins/slave-agent.jnlp
A Windows scheduled task launches the batch file on startup.
redpanda Old comment, I know, but you can use the jenkins.exe from the server as a wrapper, edit the config file and run jenkins agent as an actual windows service.
Gerhard
added a comment - - edited redpanda Old comment, I know, but you can use the jenkins.exe from the server as a wrapper, edit the config file and run jenkins agent as an actual windows service. 
I have reproduced this into two of our Jenkins masters:
In both case, I could not run a node configured as vSphere with a "Tunnel connection through" parameter; each time the port is set back to default and the server name is the jenkins server name (in our case the reverse proxy name; where no 8181 port is open).