This is what we have done to implement something similar to what you want to do. 1. Create a single script for each node/slave. It will take a parameter start or stop. These will exist on the master. 2. In the start section you will have all the commands you want to run on the VM. (We revert and start our slaves here) you will also need to connect to the slave. We use ssh to launch the slave.jar on the slave. 3. in your node setup choose the option to "run a slave via execution on master". Add the path to your script with the start parameter. 4. in the build job you will assign the node/slave that you want it to use. 5. at the end of the build you will shut down the node so when the next build tries to use it, it will need to run the script to revert and start it up again. We have created a utility build job that we call at the end of each build to do our VM shutdown. We pass in the name of the node script with the stop parameter.
Hope this helps Mark On Monday, December 10, 2012 10:28:08 AM UTC-7, Andrew Melo wrote: > > Hey all, > > I seem to remember mails about this, but I can't seem to gmail-foo the > right words to get the conversation back up. > > Is there a good way to have a slave restart/load a checkpoint after a > job is executed? I'd like to run some tests that involve provisioning > a blank machine, so I'm looking for a way to get that connected up in > Jenkins. > > Thanks, > Andrew > > -- > -- > Andrew Melo >
