Swarm slave connection resiliency and interupted builds

[David Erickson]

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

[Daniel Beck]

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

> --
> 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 jenkinsci-use...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[David Erickson]

Thanks Daniel.. this sounds like exactly what is needed.  Is it possible to test the workflow-plugin inside Jenkins without disturbing other existing jobs, and with the standard swarm client?

You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/uMSjRFqiBcY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.