Thanks Stephen for your reply, our jenkins slaves are predominantly windows, running a SSH client on windows not sure how reliable it would be, we could try pstools but ps tools come with their own perils of network issues. I tried via a Groovy script though, details of which are posted at
https://groups.google.com/forum/#!topic/jenkinsci-dev/gd7y93o02WA Could you please let us know your suggestions please on where we are going wrong. Snippet of what i have tried The groovy script i am using is +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ import hudson.model.* import hudson.node_monitors.* import hudson.slaves.* for (aSlave in hudson.model.Hudson.instance.slaves) { println('===================='); if (aSlave.name=="NodeNameTest") { println('Name: ' + aSlave.name); println('\tcomputer.kill: ' + aSlave.getcomputer().kill()); } } +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ when i run the above the jenkins slave console(jnlp) is not killed but keeps trying every 10 seconds :-(, we dont want that to happen, we just want to kill the jnlp client and bring it up again once our tests are done. When i used the below instead of kill, println('\tcomputer.disconnect: ' + aSlave.getComputer().disconnect(offlineCause = new OfflineCause.ChannelTermination())); the jnlp client of slave terminates and reconnects in few seconds. Thoughts? Thank you for your help all along On Thursday, November 21, 2013 6:46:33 PM UTC+5:30, Stephen Connolly wrote: > > why don't you turn this on its head somewhat. > > have a jenkins job that ssh's into the machine and starts the perf tests. > The perf tests then publish their results to Jenkins using the "External > Job" type which is designed for jobs that are outside of the control of > Jenkins but you want to integrate their reporting within Jenkins. > > > On 21 November 2013 13:09, Kishore RP <[email protected] <javascript:>>wrote: > >> We cannot afford to run jenkins clients exe on our slaves since they are >> used for getting performance metrics, requirement being, when we collect >> our metrics(for over an hour) we want the jenkins client to shutdown or go >> into a suspended state without taking any system resources >> however we need jenkins for CI , >> >> One way we are trying to solve the problem is to >> offload the client part to a slave manager kind of a machine that will >> keep pinging to client machine and jenkins server to keep the communication >> >> Any suggestions on how to go about this? >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
