My repository is currently blocked as I reached the 2 GB limit. However, I cannot delete some files anymore, although I have followed the guide given by Bitbucket.
Unfortunately, I have to present my results in 2 days in a very important congress, and I need an access to my Bitbucket repository as early as possible.
Many thanks for your help and best regards,
I cannot delete some files anymore
What exactly have you tried to do? This is important information for a good bug/problem report.
Particularly, have you tried pushing local changes? e.g., `git rm whatever`, then `git commit -m [why you did it]`, then `git push [remote_branch_name] [local_branch_name]`?
1/ I have tried to remove files which I don't use and which take space. Then tried to commit and push the changes, but I get always the same answer from repository:
Total 12103 (delta 5275), reused 11562 (delta 4993)
remote: repository is in read only mode (over 2 GB size limit).
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'firstname.lastname@example.org:tjyderrien/octopus.git'
2/ Then I followed the step indicated into the guide for large repositories, i.e.:
I installed and used BFG repo cleaner. I did remove the files bigger than 100 MB (but nothing was found) and I also removed once again the annoying files (all the "aims.out" files which are not useful and take ~ 400 Mo).
I tried to push the changes, it tooks hours, and then was refused by the server.
I don't know what to do. Should I create a new repository to work?
All the best,
When a repo exceeds 2GB, we only accept pushes that are clear deletions of commits. So if any new commit is added, we deny the push. It is for that exact reason that the guide to dealing with reducing the repository size starts with the section Remove the repository limitation, which recommends that you remove the last few commits from BB before running something like BFG.
I just ran an aggressive GC on your repo, which has brought down the size of your repo to 1.8 GB. Please push your post-BFG repo now (the push should work now that the repo size is lowered). Then, when the next GC is run on your repo, the size should reduce quite a bit. Also, rather than waiting for the next GC to run automatically, just ping me (reply to this comment) after you've pushed and I'll run a manual GC again.
Removing history in Git involves creating new commits, moving existing refs to point at them and pushing everything. That still means that the old commits are still in the history. They are removed when we run GC on the server. So further cleanups still require GC. Now usually, Git GC runs automatically on the servers, but it was just faster for me to trigger it manually for now.
Using LFS only means that any future large files will not be a part of the core repo history. The existing commits with references to existing blobs will still be a part of your repo. Using LFS will help the repository size from growing in the future.
I recommend watching https://www.youtube.com/watch?v=iJ3hXuEVKAc to understand LFS and how it works. It's also kinda fascinating.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs