My company is auditing Jenkins as a build system, and our use case requires us to run long builds (12 hours) on slave machines. Because a persistent network connection must be maintained with the slave machine during this whole duration, sometimes our builds fail because of network hiccups. This can be very disappointing!
Basically I'm just looking for any suggestions to alleviate these problems. I would think there is a way to start a build on a slave machine that does not require a persistent network connection. Maybe a heartbeat from the slave every once in a while, but something with a little error correction... or at least a retry timer. Any ideas? Thanks!
