youngmon/atlassian-qna huggingface dataset:
Considerable change in repository size when importing
Asked by Michael Ligotino:

Hello,

We are about to migrate to Bitbucket from GitLab. In some preliminary tests, we noticed a large difference in repository storage size when importing a project to Bitbucket from GitLab (using Bitbucket's import functionality). As an example, a 640 MB repository becomes 192 MB on Bitbucket. Everything is imported correctly, and the history seems intact. This drastic size difference remains however a bit mysterious. We would like to make sure that really nothing is lost in the process.

I would be happy to understand more rigorously the reason of this change, and would gladly take any input / advice on how to debug this.

Best regards,

p.s. we are not using Git LFS


Answers:
author: Theodora Boudale
body: Hi [@Michael Ligotino](/t5/user/viewprofilepage/user-id/5172772) and welcome to the community!

When you import a repo, all the branches and history of the .git repo will be imported (the only exception is Git LFS objects, that you are not using).

One possible reason for this discrepancy may be inaccessible commits in the GitLab repo. If you do any of the following:

* create a branch, add commits to it, push it, and then delete the branch without merging it
* alter history and push it to the remote repo (e.g. with commands like git reset or git rebase)

then certain commits will become inaccessible. These inaccessible commits remain in the remote repo unless a garbage collection runs (git gc). When a git gc runs for a repo, it can run with different parameters that determine which inaccessible objects will be deleted.

A git gc also compresses file revisions and there are parameters that control the depth of compression.

So, the size of the repo in GitLab depends on when the last garbage collection ran for that repo and with what arguments.

When you import a repo these unreachable objects will not be imported.

You can try taking a bare clone of the GitLab repo on your machine, with the command

```
git clone --bare <gitlab_repo_url>
```

Then navigate to the directory of the bare clone, and run the command

```
git count-objects -Hv
```

The sum of the fields **size** and **size-pack** in the output will show you the size of the bare clone.

Kind regards,  
Theodora

comments: author: Michael Ligotino
body: Dear Theodora,

Thank you so much for your answer. This will definitely help me understand more what is going on.

Kind regards,

Michael


author: Theodora Boudale
body: You are very welcome, Michael. Please feel free to reach out if you ever need anything else!

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud

gitlab

import

storage
Stopped receiving email notifications
Asked by Joel Joseph:

[@Theodora Boudale](/t5/user/viewprofilepage/user-id/818086)

i also have not received email notifications in the last month. Can you please check my email.


Answers:
author: Theodora Boudale
body: Hi [@joel_joseph](/t5/user/viewprofilepage/user-id/5174153)!

Your email address was also on our suppression list, so I went ahead and removed it.

Could you please keep an eye and let me know if you can receive email notifications now?

Just a heads up, I moved your post to a new question. It's best to have a separate question for each issue, as the root cause of a certain issue may not always be the same for all users; so, a question can become convoluted and difficult to follow if we try to troubleshoot multiple users' issues. Additionally, a new question has better visibility to the rest of my team, in case I am out of office.

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud
Stopped receiving email notifications
Asked by Julien Richards:

[@Theodora Boudale](/t5/user/viewprofilepage/user-id/818086) i also have not received email notifications in the last month. Can you please check my email.


Answers:
author: Theodora Boudale
body: Hi [@Julien Richards](/t5/user/viewprofilepage/user-id/5174105),

Your email address was on our suppression list, so I went ahead and removed it.

Could you please keep an eye and let me know if you can receive email notifications now?

Just a heads up, I moved your post to a new question. It's best to have a separate question for each issue, as the root cause of a certain issue may not always be the same for all users; so, a question can become convoluted and difficult to follow if we try to troubleshoot multiple users' issues. Additionally, a new question has better visibility to the rest of my team, in case I am out of office.

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud
Same here https://bitbucket.org/ayal_org/ssh-persistent-t...
Asked by ayal_org:

Same here

[https://bitbucket.org/ayal_org/ssh-persistent-tunnel/issues?status=new\&status=open\&is_spam=!spam](https://bitbucket.org/ayal_org/ssh-persistent-tunnel/issues?status=new&status=open&is_spam=!spam)

is there any way to delete the issues? Migrated to JIRA and deleted them there, but they are still present in bitbuct


Answers:
author: Patrik S
body: Hi [@ayal_org](/t5/user/viewprofilepage/user-id/5173872) ,

Thanks for reaching out to the Community!

I've moved your post to a new question for easier tracking.

Our engineering team can help with either:

* flag issues as Spam
* completely remove issues

**Please keep in mind that there is a possibility for false positives to be included in the flagging or removal.** If you are concerned about irreversible loss, we would suggest requesting flagging, so that you can review the issues.

Before we proceed, ++please make your issue tracker private++ (*Repository Settings \> Issue Tracker \> Private issue tracker*) to prevent the creation of new spam issues. I will post an update here once our engineering team has mitigated the issue and when it's safe to make your issue tracker public again.

Afterward, please let us know whether you would like us to proceed with flagging issues as spam in your issue tracker or removing them :

* **Removal**: If you would like us to proceed with the removal, please provide a range of issue IDs to remove. You could also include issues that you want to be excepted from this range. E.g. for the range "200-3700 EXCEPT 3256-3260" we will remove issues with id from 200 until 3700, except for the issues in the range 3256-3260. Ranges should be fully inclusive, meaning the number on both ends will be removed.
* **Flagging as Spam:**If you would prefer to mark the issues as Spam, so you can review them later, please provide an Issue ID as a starting point. All the issues after the starting point ID will be marked as Spam.

Let me know in case you have any questions.

Thank you, [@ayal_org](/t5/user/viewprofilepage/user-id/5173872) !

Patrik S
To run gc on bitbucket server?
Asked by stargazer33:

One of my repositories is 630MB according to "Repository details" web page.  
After running the BFG tool - I see the repository is 16M in the filesystem.

Still I see the "Repository size=630MB" in the "Repository details" web page.  
Can somebody please run gc on bitbucket server?

Repositry URL: \<repo_url_removed\>

<br />

thanks in advance!  
Dmitri


Answers:
author: Theodora Boudale
body: Hi Dmitri,

Thank you for reaching out!

I ran a git gc for your repo and its size has been reduced. Please feel free to let me know if it looks ok on your end and if you need anything further.

Just a heads up, I removed the repo URL from your post to protect your privacy.

Kind regards,  
Theodora

comments: author: stargazer33
body: It is 15.6 MB now  

Many thanks, Theodora!


author: Theodora Boudale
body: That's good to hear, thank you for the update!

Please feel free to reach out if you ever need anything else!


Tags: bitbucket-cloud

cloud
Spam on issue tracker
Asked by hairys:

Related to : <https://community.atlassian.com/t5/Bitbucket-discussions/Dozens-of-spam-issues-being-created-on-bitbucket-osrf-ariac/m-p/2302858>

+1

<https://bitbucket.org/rafzi/hacklib_gw2/issues>


Answers:
author: Patrik S
body: Hi [@hairys](/t5/user/viewprofilepage/user-id/5173398) ,

Thanks for reaching out to the Community!

I've moved your post to a new question for easier tracking.

I understand that a repo where you are a collaborator was affected by some spam issues being created. In this case our engineering team can help with either:

* flag issues as Spam
* completely remove issues

If you would like the help of our engineering team to bulk remove or mark those issues as spam, we would need an Admin of that repository or workspace to provide the consent here.

Could you please ask for an admin of that repository/workspace to post here if they consent to remove the spam from rafzi/hacklib_gw2 ?

Thank you, [@hairys](/t5/user/viewprofilepage/user-id/5173398) !

Patrik S

comments: author: hairys
body: Remove issues 50-182, inclusive. The admin has long abandoned the project and I have been maintaining it since, so it's unlikely you will get a response. I'll tag [@rafzi](/t5/user/viewprofilepage/user-id/2829570) anyway, though.


author: Suhas Sundararaju
body: Hi [@hairys](/t5/user/viewprofilepage/user-id/5173398) ,

we have resolved the spam issues from issue ID 50 to 182. We hope this helps. Apologies for any inconvenience this may have caused you.  

Regards,

Suhas
Spam attack on issue tracker
Asked by Wim Deblauwe:

I have the same issue at <https://bitbucket.org/wimdeblauwe/jdvp/issues>

An easy way to bulk delete those would be great.


Answers:
author: Theodora Boudale
body: Hi [@Wim Deblauwe](/t5/user/viewprofilepage/user-id/853283),

Thank you for reaching out.

Just a heads up, I moved your post to a new question for easier tracking.

Our development team can do either of the following:

* flag issues as Spam
* completely remove issues

**Please keep in mind that there is a possibility for false positives to be included in the flagging or removal.** If you are concerned about irreversible loss, we would suggest requesting flagging, so that you can review the issues.

Before we proceed, ++please make your issue tracker private++ to prevent the creation of new spam issues. I will post an update here once our engineering team has mitigated the issue and when it's safe to make your issue tracker public again.

Afterwards, please let me know

* Whether you would like us to proceed with flagging issues as spam in your issue tracker or removing them
* If you would like us to proceed with removal, please provide a range of issue id-s to remove. You could also include issues that you want to be excepted from this ranage. E.g. for the range "200-3700 EXCEPT 3256-3260" we will remove issues with id from 200 until 3700, except for the issues in the range 3256-3260. Ranges should be fully inclusive, meaning the number on both ends will be removed.

Please feel free to let me know if you have any questions.

Kind regards,  
Theodora

comments: author: Wim Deblauwe
body: Hi,

thank you for helping me out!

I have made the issue tracker private.

You can remove the issues 62-132 completely, they are all spam.

regards,

Wim


author: Mark C
body: Hi [@Wim Deblauwe](/t5/user/viewprofilepage/user-id/853283)

We'd just like to inform you that we've gone ahead and marked those issues from 62 to 132 as Spam.  
Right now, they're flagged as "Spam" issues, meaning, they won't show on your "Open" issues filter.  
You can go ahead and review those flagged issues by using the "Spam" in the advanced search.

Let me know if you have any further questions.

Regards,  
Mark C


author: Wim Deblauwe
body: Thanks!


Tags: bitbucket-cloud

cloud
Lerna build not supported on bitbucket pipeline.
Asked by Tomo Tomo:

I am recently try to use lerna to manage my monorepo project. Everything going well on local build but it's just not working on bitbucket pipeline.

I am keep getting error below.

```
`ERROR  Failed to compile with 6 errors6:38:31 AM`
`These dependencies were not found:`

`* @gtm-support/vue2-gtm in ./src/main.js`

`* document-register-element/build/document-register-element in ./src/main.js`

`* vue in ./src/main.js, ./src/store/index.js`

`* vue-custom-element in ./src/main.js`

`* vuex in ./src/store/index.js`

`To install them, you can run: npm install --save @gtm-support/vue2-gtm document-register-element/build/document-register-element vue vue-custom-element vuex`
```

From my understanding, We shouldn't need to have those dependency on the root package.json. It should get install through all the dependency under each packages.

Not sure if anyone having the same issue.

Here is what i have on my bitbucket-pipelines.yml.

```
pipelines:
default:
- step:
name: Build
image: node:14.20
caches: # optional
- node
script:
- npm i
- npm run bootstrap
- npm run build
artifacts:
- packages/**/dist/**
```


Answers:
author: Theodora Boudale
body: Hi [@Tomo Tomo](/t5/user/viewprofilepage/user-id/5173333),

Just to give you some context, Pipelines builds run in Docker containers. For every step of your build, a Docker container starts using the image you have specified in your bitbucket-pipelines.yml file. The repo is cloned in that container, and then the commands of the step's script are executed. When the step finishes that Docker container gets destroyed.

The step that you have in your bitbucket-pipelines.yml file will run in a Docker container that is using the Dockerhub image node with the tag 14.20:

* <https://hub.docker.com/_/node>

You can use, though, any public and private Docker image including those hosted on Docker Hub, AWS, GCP, Azure, and self-hosted registries accessible on the internet.

The error message that you get simply indicates that certain dependencies are missing from the Docker container where the build is running. This does not necessarily mean that your build is not supported in Pipelines, but that these dependencies need to be installed for your build to run.

Your local environment may have different tools or different versions of the tools you are using than the Docker container where the build is running, which would explain why your build succeeds locally. I'm not very familiar with node and npm so I'm not sure if the version of node and npm are relevant to the behavior you are seeing (in this case you could try using a different tag of the node image that has newer versions) or if the culprit is something different.

You can try installing these dependencies with the command provided in the error and see if that resolves your issue.

If you have any questions, please feel free to reach out.

Kind regards,  
Theodora


Tags: bitbucket-cloud

bitbucket-pipelines
I am also seeing a flood of spam issues at my repos: http...
Asked by djhshih:

I am also seeing a flood of spam issues at my repos:

<https://bitbucket.org/djhshih/argparser/issues>

<https://bitbucket.org/djhshih/io/issues>

Any way to mark the spams en masse?


Answers:
author: Patrik S
body: Hi [@djhshih](/t5/user/viewprofilepage/user-id/5136168) ,

Thanks for reaching out to the Community!

I've moved your post to a new question for easier tracking.

Our engineering team can help with either:

* flag issues as Spam
* completely remove issues

**Please keep in mind that there is a possibility for false positives to be included in the flagging or removal.** If you are concerned about irreversible loss, we would suggest requesting flagging, so that you can review the issues.

Before we proceed, ++please make your issue tracker private++ (*Repository Settings \> Issue Tracker \> Private issue tracker*) to prevent the creation of new spam issues. I will post an update here once our engineering team has mitigated the issue and when it's safe to make your issue tracker public again.

Afterward, please let us know whether you would like us to proceed with flagging issues as spam in your issue tracker or removing them :

* **Removal**: If you would like us to proceed with the removal, please provide a range of issue IDs to remove. You could also include issues that you want to be excepted from this range. E.g. for the range "200-3700 EXCEPT 3256-3260" we will remove issues with id from 200 until 3700, except for the issues in the range 3256-3260. Ranges should be fully inclusive, meaning the number on both ends will be removed.
* **Flagging as Spam:**If you would prefer to mark the issues as Spam, so you can review them later, please provide an Issue ID as a starting point. All the issues after the starting point ID will be marked as Spam.

Let me know in case you have any questions.

Thank you, [@djhshih](/t5/user/viewprofilepage/user-id/5136168) !

Patrik S
Keeping Bitbucket URL constant/consistent
Asked by Pam Simek:

Greetings!  

For Bitbucket Cloud is it possible to keep the repo URL taxonomy consistent across versions? Some setting that can be configured to pin this down to a consistent path across versions, for example:   

[bitbucket.org](https://bitbucket.org/)/\<org\>/\<repo\>/src/\<branch_name\>/\<file_path\>  

Thank you.


Answers:
author: Oday Rafeh
body: [@Pam Simek](/t5/user/viewprofilepage/user-id/5172411)

In Bitbucket Cloud, the URL structure for accessing files in a repository is relatively consistent across branches. The only part that varies is the \<branch_name\> in the URL. To access a specific file within a branch, you can use the following URL structure:

```
https: //bitbucket. org/<org>/<repo>/src/<branch_name>/<file_path>
```

However, when browsing files in Bitbucket Cloud, the URL will also include a commit hash or a reference ID. This is to ensure that the content displayed is associated with a specific commit, even if the branch changes over time. The URL will look like this:

```
https: //bitbucket. org/<org>/<repo>/src/<commit_hash_or_reference_id>/<file_path>? at=<branch_name>
```

Unfortunately, there is no built-in setting in Bitbucket Cloud to change this behaviour or simplify the URL structure.

If you need a consistent URL format for automation or external tools, you can use the Bitbucket Cloud REST API. For example, to access a file in a specific branch, you can use the following API endpoint:

```
https: //api. bitbucket. org/2.0/repositories/<org>/<repo>/src/<branch_name>/<file_path>
```

Using the REST API ensures a consistent URL structure when accessing files in different branches.

comments: author: Pam Simek
body: Thanks much Oday, much appreciated.


author: Oday Rafeh
body: You're more than welcome !!


Tags: bitbucket-cloud

cloud
Spam attack on issue tracker
Asked by togiles:

Our repo is also being targeted, I turned off anonymous posting but there are hundreds added and removing then one at a time is ... well annoying at best!

<https://bitbucket.org/togiles/lightshowpi/issues>

[@Theodora Boudale](/t5/user/viewprofilepage/user-id/818086) can you help me as well?


Answers:
author: Theodora Boudale
body: Hi [@togiles](/t5/user/viewprofilepage/user-id/5173253),

Thank you for reaching out.

Just a heads up, I moved your post to a new question for easier tracking of your issue.

Our development team can do either of the following:

* flag issues as Spam
* completely remove Spam issues

**Please keep in mind that there is a possibility for false positives to be included in the flagging or removal.** If you are concerned about irreversible loss, we would suggest requesting flagging, so that you can review the issues that are flagged.

Please let me know:

* Whether you would like us to proceed with flagging issues as spam in that issue tracker or removing them
* If you would like us to proceed with removal, please provide a range of issue id-s to remove. You could also include issues that you want to be excluded from this range. E.g. for a range "200-3700 EXCEPT 3256-3275" we will remove issues with id from 200 until 3700, except for the issues in the range 3256-3275. Ranges should be fully inclusive, meaning the number on both ends will be removed.

Please feel free to let me know if you have any questions.

Kind regards,  
Theodora

comments: author: togiles
body: All issues added in the last 4 days should be removed, starting from <https://bitbucket.org/togiles/lightshowpi/issues/129>

Thank you!


author: Theodora Boudale
body: Hi [@togiles](/t5/user/viewprofilepage/user-id/5173253),

Could you please provide the issue id at the end of the range? We need that as well and I don't have access to your issue tracker to check.

Thank you,  
Theodora


author: togiles
body: 129 -\> 294 are all spam


author: Mark C
body: Hi [@togiles](/t5/user/viewprofilepage/user-id/5173253),

We'd just like to inform you that we've gone ahead and marked those issues from 129 to 294 as Spam.  
Right now, they're flagged as "Spam" issues, meaning, they won't show on your "Open" issues filter.  
You can go ahead and review those flagged issues by using the "Spam" in the advanced search.

Let me know if you have any further questions.

Regards,  
Mark C


author: ecoRoland
body: [@Theodora Boudale](/t5/user/viewprofilepage/user-id/818086)May I direct your attention to all the posts regarding this issue in this question?

<https://community.atlassian.com/t5/Bitbucket-discussions/Dozens-of-spam-issues-being-created-on-bitbucket-osrf-ariac/m-p/2302858#M3977>

Many repos have been spammed and need clean-up.


Tags: bitbucket-cloud

cloud
my engineer cannot receive invitation email
Asked by Aoday Mohammad:

Hi there,

I hope this message finds you well. I am reaching out because I recently sent an invitation to one of my engineers, but it seems he has not received it yet. Despite checking various folders such as spam, junk, and webmail, I have been unable to locate the invitation.

I apologize for any inconvenience this may have caused and I would appreciate any suggestions or assistance you may have in resolving this issue. Thank you for your time and attention.


Answers:
author: Syahrul
body: G'day, [@Aoday Mohammad](/t5/user/viewprofilepage/user-id/5173062) and welcome to the community!

I have raised a support ticket on behalf of you so we can continue investigating it.

Please view your ticket [here](https://support.atlassian.com/requests/BBS-200101/)

Cheers,  
Syahrul


Tags: bitbucket-cloud

cloud
How to use a custom image on a self hosted runner as the pipeline Image
Asked by Anthony Bou Eid:

Hello,  

This is the scenario I have.   
I'm using a linux machine as a self hosted agent. On this agent I have a custom Image that has all my requirements.  
Is there a way to specify in the bitbucket-pipeline.yml file to use this image?  

For example in github I would do:  

runs-on: self-hosted-linux # self hosted agent tag  
container: my-custom-image:latest  

Container here specifies the image that already exists on self-hosted-linux and tells the pipeline to create a container from that image and use it as an image for the pipeline.   

Is there an equivalent in Bitbucket?  
Thanks!  


Answers:
author: Ben
body: Hey Anthony,

Custom docker images used in your build environment are only compatible with Linux Docker runners, it is not supported within Linux Shell environments.

Here is some documentation to assist you further:

* <https://support.atlassian.com/bitbucket-cloud/docs/set-up-and-use-runners-for-linux/>
* <https://support.atlassian.com/bitbucket-cloud/docs/configure-your-runner-in-bitbucket-pipelines-yml/#Custom-docker-in-docker-image>

Cheers!

- Ben (Bitbucket Cloud Support)

comments: author: Anthony Bou Eid
body: I tried the approach foudn in the 2nd link:  

definitions:  
services:  
docker-custom:  
type: docker  
image: private-image (this is the image that is on the self-hosted linux machine)

pipelines:  
default:  
- step:  
name: test  
runs-on:  
- 'self.hosted'  
- 'linux'  
services:  
- docker-custom  
script:  
- python3 main.py  

This throws an error saying that I have to authenticate with my Azure Container Registry to use the image... It doesn't use the image that is found on the machine

<br />

<br />


author: Ben
body: Hi Anthony,

Can you try reference the image like this if it is hosted locally?

```
 name: localhost:0000/imagename
```

Where 0000 is the port number and imagename is the name of the image.

Cheers!

- Ben (Bitbucket Cloud Support)


Tags: bitbucket-cloud

bitbucket-pipelines

cloud