My original purposes were to use a build server to build computer
appliances. While removing the JAR file is not absolutely necessary for the
functionality of the appliances as their presence it not a hindrance on
that functionality, it would be preferable to have no files that are
unnecessary for that functionality.
Thank You,
Andrew
On Friday, January 4, 2013 10:11:19 AM UTC-8, Mandeville, Rob wrote:
>
> 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)
>
