Do you mean installing a slave or launching it?
A slave is simply a .jar file. Copy it where it needs to be, make sure you
have a JVM that can run it, and you’ve installed it.
I have a number of slaves set up with “launch by running a command on the
server”. Said command just ssh’s to the target host as the right user and runs
“java –jar slave.jar”. At least in Unix (my forte), you can set up a launcher
command like “ssh remote_host \”curl {right args to get slave.jar from the
Jenkins server} && java –jar slave.jar”. The actual command, and what it would
take on other platforms, is left as an exercise to the reader.
As far as uninstalling goes, I don’t think so. I don’t think there’s a
“trigger this job on shutdown” command. Is there a real need to delete
slave.jar from the remote machine after shutting down the slave?
--Rob Mandeville
Litle & Co (a member of the Vantiv family)
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Andrew Bayless
Sent: Friday, January 04, 2013 12:55 PM
To: jenkinsci-users@googlegroups.com
Subject: Two quick questions about slave nodes.
Hello,
I have two quick questions about Jenkins slaves:
1) Is it possible to have Jenkins install a slave on a machine remotely ?
2) Is it possible to have a slave uninstall itself ?
Thank you,
Andrew
The information in this message is for the intended recipient(s) only and may
be the proprietary and/or confidential property of Litle & Co., LLC, and thus
protected from disclosure. If you are not the intended recipient(s), or an
employee or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any use, dissemination, distribution or
copying of this communication is prohibited. If you have received this
communication in error, please notify Litle & Co. immediately by replying to
this message and then promptly deleting it and your reply permanently from your
computer.
