-
Notifications
You must be signed in to change notification settings - Fork 34
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
Bandwidth Caps for Git LFS #28
Comments
This offers some hope |
Thanks for that. I believe this fix is only valid if the directory you're building with Travis is the one under Git LFS. That is, if I'm building my However my setup is as follows:
I could move the test data into the I think this is what will end up happening but thought I'd throw it out there first... |
@jacobseiler You could also also automate that extra step under a |
In my cache:
directories:
- tests/rsage_testdata/ This will then cache all of the test data and ensure that it won't be pulled for every Travis build. I've moved away from Git LFS because the bandwidth is repository specific. So if you made a fork of Feel free to close the issue. |
I recently started tracking a large file using Git LFS. It's only a single file that is ~128Mb in size.
The repository is connected to my tests so each time I want to build my code on Travis it has to access the large file. After working for a few hours, I got an email stating
This seems to say that I can only
git clone
the repo a certain amount of times before I go over the bandwidth limit? I'm absolutely baffled by this...Does anybody have any experiencing using Git LFS and care to offer some help?
The text was updated successfully, but these errors were encountered: