Whenever you clone a git repository, git copies all of the objects from the
original repo to the ".git" directory in the clone, along with the clear-text
files of the branch you are cloning.
This is a major problem with git scalability, and there are various
workarounds, including shallow clones.
One that I like, is to import your git repository into Perforce via the Git
Fusion addon, and then break up the repository into multiple smaller git
repositories using Perforce client views (we call this "slice and dice").
Of course, once your source is in Perforce, you can always just use the
Perforce client views directly in Jenkins, and avoid copying the Git meta
directory altogether. This is much faster for a build checkout.
Another advantage of using Perforce to store your git repositories is, it is
scalable - i.e., you can replicate your git repos via Perforce replicas and
edge servers. Perforce stores the git objects unmolested as binary objects, so
you can always recreate the original repository anywhere you have a replica.
(We do this at Perforce - we use a "build farm" replica exclusively for build
checkouts).
I gave a webinar on the "slice and dice" technique a while back:
http://www.perforce.com/resources/presentations/webinars/dev-talk-avoid-git-bloat-submodule-hell
I also did a tutorial on setting up and exploring Git Fusion:
http://www.perforce.com/blog/130702/using-git-api-perforce-part-1
cheers,
-Russ
At 11:50 PM -0700 7/18/14, bandi pavankumar reddy wrote:
>Hi friends i am trying to clone 18 GB repository in Jenkins it's giving time
>out error and i already mentioned timeout 60 minuets i n 13 th minute it'
>displaying time out error ...give me any suggestions it is possible or not
>
>--
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
