As I understand from JIRA description, the user is trying to start a slave and it neither goes to success or failure, the process just hangs.
Even though Jenkins has retry mechanism, it will not be engaged until the original call is returned with failure status. What the user is suggesting: - to add timeout mechanism, so when the call is stuck, Jenkins will timeout it - essentially auto-kill for the call and then retry the call - to add kill ability, so someone manually will be able to cancel the call I believe first we should verify why is it happening without adding more features to Jenkins. It is definitely an environmental issue as nine of other slaves are working just fine. We can first ask user to increase log level and debug the process. Once the cause is identified then this "bug" can be converted to "feature" and implemented, which should not be that complicated. Or maybe just implement it right away :-) Anyway, great idea to bring it to the governance meeting. I just started to participate in Jenkins developer and might not know all the possible workflows. On Jul 5, 2012, at 6:01 AM, Albin Joy <[email protected]> wrote: > Hi All, > > I found one issue https://issues.jenkins-ci.org/browse/JENKINS-13237 on > jenkins regarding the master-slave connection retry. And this issue is still > open. > > I read, Jenkins mster-slave connection already have retry mechanism. But then > also why there is a Jira like this? Is there are problem related to > master-slave retry? > > Thanks for your supports.. And expecting the same again... > Thanks in advance...
