A plugin with that feature is part of Jenkins Enterprise. http://release-notes.cloudbees.com/product/CloudBees+Long-Running+Build+Plugin
Something similar will also be part of the upcoming workflow-plugin. https://github.com/jenkinsci/workflow-plugin On 03.10.2014, at 04:13, David Erickson <[email protected]> wrote: > Hi we are using the swarm plugin to connect slave nodes from the cloud over > vpn to our master Jenkins server. We've noticed that occasionally the VPN > connection is temporarily interrupted, which causes the TCP connection from > the slave to the master to fail, and kills any running build(s). This forces > us to manually re-run any builds which were in progress, which can > potentially be a lot depending on the scope of the network interruption. The > ideal behavior is that the job that was running on the slave(s) continues to > execute until completion, and waits for the connection to be re-established, > and picks up where it left off in execution order. Is there any way to > enable this? It seems like a very important capability to have. > > Thanks! > David > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
