Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Allow for repository updating rather than full clone every time #347

Closed
Mrono opened this Issue Jan 31, 2014 · 8 comments

Comments

Projects
None yet
4 participants

Mrono commented Jan 31, 2014

For those of us who have large repos (1.3Gb here) a clone takes a good chunk of time. It would be better to have the repo downloaded into a cache and used multiple times and just run reset, clean, fetch, etc to keep it in a sanitary state without having to get the whole thing every time.

shfx commented Jan 31, 2014

👍

Mrono commented Jan 31, 2014

this also applies to #348

Owner

niallo commented Jan 31, 2014

Isn't this already possible with the various caching modes? /cc @jaredly

On Friday, January 31, 2014, Mike notifications@github.com wrote:

this also applies to #348#348

Reply to this email directly or view it on GitHubhttps://github.com/Strider-CD/strider/issues/347#issuecomment-33826166
.

Niall O'Higgins
W: http://niallohiggins.com
E: n@niallo.me
T: @niallohiggins

Owner

jaredly commented Jan 31, 2014

yes this is implemented

Mrono commented Jan 31, 2014

How do I use it, I didn't see any docs on it.

Owner

jaredly commented Jan 31, 2014

In the provider config section.

image

But it looks like the standard git provider hasn't implemented it -- sorry about that. I'll get that in this weekend.

@jaredly jaredly referenced this issue in Strider-CD/strider-git Jan 31, 2014

Closed

implement caching #3

Mrono commented Jan 31, 2014

I'm using custom provider, internal gitlab server. That option is not available, only keys and url

Owner

jaredly commented Jan 31, 2014

Yup. I'll implement that on the strider-git plugin this weekend, and everything should work out for you.

@ghost ghost assigned jaredly Jan 31, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment