|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Thanks for the pointer, but I don't think the implementation in the Perforce plugin will help. There is already a timeout implementation in the code path used by the Git plugin.
I don't understand the code well enough to find the implementation.
I assume the message that is displayed is being reported by the joinWithTimeout() method in Jenkins core since it is the only java location in the jenkins, git-plugin, and git-client-plugin directories with the string "Timeout after". Unfortunately, I can't find any callers to that method. I was hopeful that others could find that and provide a pull request for consideration.
Alternately, maybe there is a better way to implement the timeout such that it will reset the timeout counter each time data is received from the external process. I thought that was how it was implemented prior to git plugin 2.0, since this problem did not appear until git plugin 2.0.