Jenkins Master slave connection issue

[Arvi]

Hi All, 

We are using Jenkins model of Upstream-downstream builds. 
I have number of Slaves hosted in a remote office and the tests are triggered by Main build. These tests runs for hours. 
The issue I have is, some times we see network blips which disconnects slave for few seconds 
and the whole build is lost and have no way to retrieve it or restore the build back once the connection is re-established. 

Is there anyway in Jenkins to handle such network blips !? 
May be using the Process ID and tracking or something or I'm I missing some key configurations? 
Its really painful to kill all the stray jobs from previous build, then re-kick the jobs and  wait for hours. 

Appreciate your help, 
Thanks!

[Mandeville, Rob]

As far as I can tell, Jenkins slaves cannot handle connectivity blips.  I think that it assumes LAN connectivity.  Maybe you can ask your network admin and see if there’s a way to keep those connections up, or at least make it look like they are.

 

Failing that, can you put a second Jenkins server on the remote site?

 

--Rob

--
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/groups/opt_out.
 
 

The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle & Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle & Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.

[Aravind H S]

Regarding Second instant of Jenkins :
yes, have considered getting a second Jenkins Server.
But did not want users to login to different urls or in other words want to create one single page to see status of whole build flow.
Any suggestion on that line?

Thanks!

--
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/2WRu8rhoNuI/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.

[Mandeville, Rob]

Haven’t tried this, but I dug this plugin up:

 

https://wiki.jenkins-ci.org/display/JENKINS/Build+Publisher+Plugin

 

It was originally built so that you could have a Jenkins instance outside a firewall report on builds for a second instance inside a firewall, giving the world read-only access to your builds.  Thus, they talk about “private Jenkins” (the host doing the builds) and “public Jenkins” (the host publishing the result).  Your setup would involve setting up your remote site as the “private Jenkins”, and the one you already have set up would be the “public Jenkins”.  This way, users would still only have to look at the local server.

 

--Rob

[Aravind H S]

I will give it a shot..
Thanks Rob!

[Sami Tikka]

Sometimes you might be able to use "external jobs": https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+external+jobs

They aren't as feature rich as normal jobs, but maybe you can use it as a workaround.

-- Sami