|
||||||||
|
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/d/optout.
Having spent days trying to track this down with our team, I thought I'd post in efforts to help others when this occurs. I'll explain as best I can, but I didn't actually fix the problem, so I may not have everything dead-on.
In our case, we had contention between two instances of git running at the same time through SSH. The first instance would run, and the second would somehow get blocked when reading the known_hosts file and ask you to authenticate, causing the plugin to just sit there until the timeout occurs.