Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manage one checkout for all projects #1375

Closed
ericholscher opened this issue Jun 24, 2015 · 3 comments
Closed

Manage one checkout for all projects #1375

ericholscher opened this issue Jun 24, 2015 · 3 comments
Labels
Accepted Accepted issue on our roadmap Improvement Minor improvement to code

Comments

@ericholscher
Copy link
Member

There would be a sizable win if we changed from having a checkout for every version of a project to having one central checkout, that gets cloned and then deleted into each version on build. This would save lots of bandwidth and disk space, because we could keep a much larger cache of clones.

The main space issue is actually around the virtualenvs, but this would be a good start to addressing this.

@humitos
Copy link
Member

humitos commented Jan 22, 2019

We already implemented #4939 that forces git to download only the latest 50 commits. It's not exactly the same as what this issue proposes but it's related.

Considering that we are removing all the checkouts at the end of the day if not recently updated, I suppose that by having only one checkout for all the versions we are not going to gain too much space here.

@stsewd
Copy link
Member

stsewd commented Mar 1, 2019

This would be useful if we save the one checkout in one server/location, right now we have several builders and it wouldn't make much difference if we save one checkout per builder.

@humitos
Copy link
Member

humitos commented Mar 4, 2019

We are talking about having volatile servers in the middle term because different reasons (disk costs, reproducibility, etc), so I think this issue is not valid anymore. I'm closing it here.

@humitos humitos closed this as completed Mar 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Accepted issue on our roadmap Improvement Minor improvement to code
Projects
None yet
Development

No branches or pull requests

5 participants