|
||||||||
|
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.
Are you certain that commit 79c8eb3d846d09ecedf3b331942d8904cdedf515 is available in the repository where you are trying to perform the checkout?
The "Could not checkout null" might be better phrased as "Could not checkout a detached head". It is a known, and expected behavior that the git plugin uses a detached head unless it needs a branch for other purposes.
Since the output also says that the connection timed out after 10 minutes, you may want to check if the correct credentials have been assigned to the downstream job.
Another possibility is to check that you don't have a very large git repository or are using a slow connection so that the clone actually takes more than 10 minutes. If either of those is the case, then you can increase the timeout through the "Additional Behaviours" button where you add "Advanced clone behaviours". There is a field which can adjust the timeout there.