'How to make Jenkins build _not_ fail is ssh connection between master and worker goes down?

Most questions ask: "how to make sure the remoting connection to not fail".

Instead, I am asking: "how to make sure the Jenkins build will continue to run when the connection fails".

One option may be to nohup the build script, example:

echo "some setup code"
nohup ./long_running_test.sh

With nohup, assumption is process will run to completion whether or not parent process (slave.jar) is alive or not.

However! long_running_test.sh may produce artifacts that would be consumed by a post-build task. Is it possible to recover?

Are there other suggestions other than nohup?

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Solution	Source