Hey Guys, We have a Jenkins ver. 1.652 <http://jenkins-ci.org/> version installed and automatic JNLP slave agent service was down still that node was connected.
Is this enhancement keeping slaves up and running ? https://jenkins.io/changelog/ 1.553 (2014/03/02) “Slave started from Java Web Start can now install itself as a systemd service.” Secondly, the installed service has user logon details as our tests needs some user context to get pass. But, due to this change our tests are failing ? Any thoughts, how can we avoid such situations ? or can we pass user credentials to "*systemd service*"? <https://lh3.googleusercontent.com/-_8XsIkfi9Ik/VwNTLGvMpCI/AAAAAAAAKhg/xtre3NeQ8s8fiCXrlO-dw025upqBJmYMg/s1600/Untitled.png> Thanks, Swapnil. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2f8705df-8e03-4b0b-9cc3-018780d98bc4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
