[JIRA] (JENKINS-47821) vsphere plugin 2.16 not respecting slave disconnect settings

[john.mel...@esentire.com (JIRA)]

Title: Message Title

John Mellor commented on JENKINS-47821   Re: vsphere plugin 2.16 not respecting slave disconnect settings Yes, exactly. I never do incremental builds as they are a severely-broken dev practice. I typically setup a node to disconnect after one build, and reset back to a vmware snapshot upon restart. That way I can easily debug a build problem because the machine is left in the state where the build failed, and the next job does not have artifacts present like dependency packages, config files or docker images added by the previous build. However I am now in a situation where sometimes a queued build runs on the node without going through the reset-back-to-snapshot step, breaking it. I have a crude workaround of powering the node down after every build, forcing it to go through the power-up steps which will then revert back to snapshot. However, this maximizes the downtime for the node between builds, and prevents some debugging actions because you lose the in-memory structures this way. Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.