|
||||||||
|
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.
Since you mentioned that you were updating from a much earlier version, I wonder if the much earlier version was prior to credentials support.
Have you added a credential to that repository so that when the remote polling occurs (usually on the master node), it is not relying on an existing ssh configuration on the master node? The 1.x versions of the git plugin did not support the credentials plugin within the user interface, but the 2.x versions of the git plugin include support for the credentials plugin so that you can add your private key to Jenkins for using during remote polling and checkout.
If that fixes it, then the bug is that the polling log did not clearly state that the git ls-remote command failed (since it would have failed due to no authorization). If that fixes it, then an additional enhancement would be some optional additional debugging support to identify the failure mode more clearly in the polling log.