Pipeline jobs already have that behavior. Pipeline durability settings allow the PIpeline job to continue running on a disconnected agent.
On Tue, Mar 19, 2019 at 8:21 AM <matevz.lan...@borea.si> wrote: > Hi, > > I would like to ask whether there is a good solution for scenarios when > there is a bad connection between master and slaves. I have a problem with > long duration tasks where they last for long time. If network problem > happens the task fails. It would be good enough for master to reconnect to > the slave and fetch the output accumulated in the meantime. > The network interruption is so long that SSH connection will drop. > So looking for some kind of screen+detach scenario. > > best regards, > Matevz Langus > > -- > 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-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/2d0ad876-df0e-42c1-8ae0-d9ea0a0147b4%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/2d0ad876-df0e-42c1-8ae0-d9ea0a0147b4%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Thanks! Mark Waite -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGiLeQeUP9_%2BmPR_wSQvO16h13bNz0mQxyZwaDW6D1w7Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
