|
||||||||
|
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.
I will definitely need more information to duplicate the problem. The log file hints that the "fetch" may be completing and then the "checkout" is failing. That is quite uncommon, since the fetch is a network operation and the checkout is a local file system operation, and usually the network operation is much slower than the file system operation.
Are you in an environment where the file system checkout might take a very long time? If so, can you perform the operations you need to perform without using the entire tree? The git plugin supports "sparse checkout" where you can checkout a subset of the directories in the repository to make the checkout process faster (and use less disc space). As an example, we have an 8 GB repository but only need a very few directories. With a reference repository and a sparse checkout, we can complete the clone and checkout in 10-20 seconds, rather than waiting the many minutes to fetch the whole history and checkout the entire repository.