The latest version of the plugin shutdowns a slave, no matter if a job is running or not, if Jenkins master looses the network connection with the slave. This should not happen because Jenkins slaves are capable of reestablishing it.

      The root of the problem is that the slave shutdown happens in VirtulMachineLauncher.afterDisconnect(), triggered everytime when the connection between master and slave goes down. The provided patch fixes that.

          [JENKINS-19531] Slave should be shut down only if idle

          G. Kr. added a comment -

          G. Kr. added a comment - already solved https://github.com/jenkinsci/libvirt-slave-plugin/pull/7#event-92245324

            tastybug Philipp Bartsch
            pedjak Predrag Knezevic
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: