Hi @yossi120
I have attempted to reduce the size of your largest repositories by executing a garbage collection, but it has not reduced the size much, and your workspace is still > 1GB:
415mb > 415mb
377mb > 377mb
255mb > 255mb
207mb > 204mb
163mb > 142mb
You have a couple of options to resolve this:
Option 1 - Delete & recreate the repositories
This is the fastest way to solve the problem, but loses metadata such as PRs, Pipelines, Permissions, etc.
1. Perform a clone of those repositories for backup purposes
2. Delete those repositories from your workspace to free up space and allow you to push. NOTE: This will permanently remove metadata such as PR's/pipelines/user permissions etc.
3. Identify the largest files in your repositories by executing the following command:
git rev-list --objects --all \
| git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' \| awk '/^blob/ {print substr($0,6)}' \
| sort -r --numeric-sort --key=2 \
| numfmt --field=2 --to=iec-i --suffix=B --padding=7 --round=nearest
3. Perform cleanup operations locally to reduce the size
4. Once complete, push those repositories back to your workspace by creating a blank repository with the same name of the deleted repository, then mirror pushing the contents of the cleaned repository:
HTTPS
git push --mirror https://<username>@bitbucket.org/<WorkspaceID>/<RepoName>.git
SSH
git push --mirror git@bitbucket.org:<WorkspaceID>/<RepoName>.git
NOTE: This will remove metadata such as PR's/pipelines/permissions etc but will keep your commit history and binary files intact.
Option 2 - Temporarily upgrade
1. Upgrade to a paid plan and utilise our 30-day trial period to restore functionality and provide more time to reduce your repository directly without deletion. You can choose to continue or cease your trial before the end of the 30-day period.
2. If you encounter any issues during this period - you may raise a ticket directly with our support team using your workspace URL:
https://support.atlassian.com/contact/
Please let me know how this goes.
Cheers!
- Ben (Bitbucket Cloud Support)
Hi @yossi120 welcome to the Atlassian community.
The answer to your question is: "No, we can't directly run git gc
on your repositories hosted on Atlassian's servers".
To my understanding, you don't have direct shell access to the servers that host your Git repositories with Atlassian. Running server-side commands like git gc
is handled by Atlassian's infrastructure, not by individual users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i know that,
i was ask if you can do it for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, okay, good to know that!
We community members will not be able to do that with your ask.
As @Tansu Akdeniz has redirected your query to the Atlassian support, they are the right team to troubleshoot your issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @yossi120
Welcome to the community!
The Atlassian support team has been notified and they will reach out to you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.