|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Cool. That's a nice additional option in git. Sounds like it does equivalent to running a git repack -a afterwards, but probably a lot more efficient. Unfortunately, it'll be a while before 2.3 is available on many of the build agent systems, where 'git repack -a' works now.
I'm just looking for something that would remove the dependency on the referenced repo after the cloning - to use it purely as a cache and not for live use. (Would be even nicer if the git plugin had some way of caching the repo on the master, but that's a major functionality change.)
Seems like a checkbox to repack would be easy/simple way to accomplish that.