I have just setup a powershell script for windows slaves that install 
everything required for builds and automatically connects the slave to it's 
master based on the parameters given when the script was executed. This 
works fine until I close the powershell window or need to reboot the 
computer. Immediately when I close the window the slave connection dies.

I haven't got much experience with this JNLP connection so I have a few 
questions. Does the web interface version reconnect when the slave machine 
is rebooted? Would there be any differences between a manual connection and 
the scripted one if the script output was hidden in a background process? 
And the biggest one, how do people manage holding persistent connections 
between master and slave where the slave machine might be restarted?

My current idea was to instead of launching the connection at the end of 
the script save it in a executable and execute that everytime the machine 
is booted.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b465b78e-997e-491b-84e7-27b5b8c56c0e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to