[
https://issues.jenkins-ci.org/browse/JENKINS-12163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160062#comment-160062
]
nyoung02 commented on JENKINS-12163:
------------------------------------
I have a similar (identical?) use case.
I have a pool of slave machines, each with a set of snapshots, running under
vSphere.
I have a number of build and test jobs, each of which require a slightly
different configuration (snapshot).
What I want to do is have these machines switched off until required, and when
a job is initiated, it picks up the next available (offline) slave, resets the
slave VM to the specified snapshot, and then starts it up. When the job is
finished, it then closes down the machine and disconnects the slave.
This would probably work with the delayed shutdown and I'll give that a go, but
it would be better (cleaner and more reliable) if there was a tick box option
in the job configuration that allowed us to close the machine on completion of
the job. The other alternative is if the slave configuration could be modified
to allow a reset snapshot option between jobs.
Background: Our test process depends on the machine being clean at the start -
if it's not we get phantom test failures. This means it's essential that the VM
is reverted to snapshot at the start of the run. Currently have the option set
to shut down the VM if it's idle for 1 minute, but if we have jobs queued up,
there is no idle time and so therefore we end up with invalid test runs.
> Cleaning VM before start next job in queue.
> -------------------------------------------
>
> Key: JENKINS-12163
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12163
> Project: Jenkins
> Issue Type: Bug
> Components: vsphere-cloud
> Reporter: Alexey Larsky
>
> Sylvain Chagnaud says: Hi, it's a very useful plugin. But I have a little
> comment for a specific case. ...
> Hi, it's a very useful plugin. But I have a little comment for a specific
> case. In fact I want to revert to a snapshot before each job execution but if
> several jobs try to run on the VMWare at the same time then the VMWare can't
> revert to the snapshot. Do you have a solution, thank you ?
> jswager - says: At the moment, I don't have a solution incorporated into the
> plugin. But I...
> At the moment, I don't have a solution incorporated into the plugin. But I'm
> working on it. In the meantime, here's a workaround:
> 1) Configure the slave with a disconnect type of Revert or Reset.
> 2) In your test job, mark the slave temporarily offline. This will prevent
> further jobs from targeting the slave. It would be something like this:
> curl -d
> "offlineMessage=back_in_a_moment&json=%7B%22offlineMessage%22%3A+%22back_in_a_moment%22%7D&Submit=Mark+this+node+temporarily+offline"
> http://JENKINS_HOST/computer/NODE_TO_DISCONNECT/toggleOffline
> 3) As a final step in your job, start a delayed shutdown of the VM. If it's
> Windows, something like "shutdown /s /t
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
