[
https://issues.jenkins-ci.org/browse/JENKINS-12163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162259#comment-162259
]
SCM/JIRA link daemon commented on JENKINS-12163:
------------------------------------------------
Code changed in jenkins
User: Jason Swager
Path:
pom.xml
src/main/java/org/jenkinsci/plugins/vSphereCloudLauncher.java
src/main/java/org/jenkinsci/plugins/vSphereCloudRunListener.java
src/main/java/org/jenkinsci/plugins/vSphereCloudSlave.java
src/main/resources/org/jenkinsci/plugins/vSphereCloudSlave/configure-entries.jelly
src/main/webapp/slave-LimitedTestRunCount.html
http://jenkins-ci.org/commit/vsphere-cloud-plugin/cc473a3d10142042bf1d53e139c3302b0be494be
Log:
Changes to address JENKINS-12163: Clean the VM after X many builds.
> 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
