Caroline R Atlassian Team

Hi, @[deleted]! Thanks for your confirmation, I'm glad to know everything is working now! Kind regards, Caroline

Hi, John, welcome to the community! I checked the email you shared here and confirmed it had a block on the server that prevented emails from being sent to them, so I removed this email from the suppression list. Just to give you some context around this issue, it can occur when the system tries to send an email to the…

Hi, @capuromeyer, thank you for reaching out to Atlassian Community. Just to complement Robert’s answer, in order to change your authentication method in Git, you can change the remote URL of your repository (you can switch it to SSH/HTTPS). In order to modify that, you can run the following commands: 1. From a terminal,…

Hi, @Sang woo Ham, welcome to the community! I ran the GC against your repository and managed to reduce its size. Just to give you some context around the reason your remote repository size didn’t change after you removed commit history and files, it happened because the remote repo still had these old references, so the…

Hi, @ChuckieAJ! Thank you for reaching out to Atlassian Community. I found the repository that was showing 1GB on your workspace, so I ran the GC against this repo and managed to reduce its size. Just to give you some context, the GC runs periodically on the server, so unless the auto GC has not been run on the server and…

Hi, @Carol, welcome to the community! Currently, script definitions are not supported. We do have a feature request to add the ability to use script entity for YAML anchors as you can see here: * https://jira.atlassian.com/browse/BCLOUD-20417 I would suggest that you add your vote there (by selecting the Vote for this…

Hi, @Santosh Kori, thank you for reaching out to Atlassian Community. Could you please test your Pipelines build locally in a Docker container and see if it’s happening there as well? You can follow the steps described here: * https://support.atlassian.com/bitbucket-cloud/docs/debug-pipelines-locally-with-docker/ Looking…

Hi, @Kunal Modi, thank you for reaching out to Atlassian Community. The link you have shared is related to Bitbucket Data Center and Server. By the screenshot you added, I understand you are working on Bitbucket Cloud, is that correct? If that's the case, currently merge checks are only available at the repository level on…

Hi, @ChuckieAJ, thank you for reaching out to Atlassian Community. That is correct, when using basic authentication in Git over HTTPS, you will need to use Bitbucket app passwords. However, if you are using the SSH format in your repository, you can continue to use your ssh key. In case you would like to read more about…

Hi, @[deleted], thank you for reaching out to Atlassian Community. I performed an analysis on our logs and confirmed that your email had a block on the server that prevented emails from being sent to you. This can occur when the system tries to send an email to the user and the account does not exist, is not activated yet,…

Hi, @Dev, welcome to the community! The “Something went wrong" message usually comes with a 5xx response that shows a Sentry ID code. This code may give us some indication of what is causing this error message. In this case, could you please follow the next steps to find the Sentry ID the next time you merge a PR, so I can…

Hi, @Bitwise DEVS. Allow me to reply to each of your questions directly and feel free to share any further concerns about the information I will share with you. 1. Can I use my Bitbucket account for Git credential when pushing just like how I use my Github when using HTTPS? It was register with Sign in via Gmail/Google…

Hi, @[deleted], welcome to the community! I confirmed that the Bitbucket account linked to the email you used to create this account was flagged as inactive. I have now reactivated this account, could you please try to access it and let me know how it goes? Kind regards, Caroline 

Hi, André! You're welcome! Have a good day too! Kind regards, Caroline

Hi, @anoel_reactif, welcome to the community! Just to give you some context around this behavior, this limit is set to prevent abuse, requiring us to validate if it's an actual person with a real need for that. I went ahead and exempted your workspace, so you should be able to create more than 300 repositories now. Please…

Hi, @Tim Apps, thank you for reaching out to Atlassian Community. Currently, it’s not possible to disable or limit the visibility of Pipeline artifacts so they cannot be downloaded. However, we already have a feature request to restrict the download of Pipelines artifacts as you can see here: *…

Hi, Simon. Thanks for sharing the additional details about your request. I have created the following feature request to add the option to retrieve artifacts from failed builds: * https://jira.atlassian.com/browse/BCLOUD-21636 We suggest that you add your vote there (by selecting the Vote for this issue link) as the number…

Hi, Jesús, thanks for your confirmation, I'm glad to know it worked. Kind regards, Caroline

Hi, @Jesús Gutiérrez, thank you for reaching out to Atlassian Community. I checked our logs and confirmed that your email had a block on the server that prevented emails from being sent to you. So I removed your email from this suppression list. Could you please confirm if you receive the notifications now? Kind regards,…

Hi, Paul. This GUI client is not developed by Atlassian, so we’re not aware of all options related to authentication and also if there are differences in different versions of the product. Such a manual/guide would need to be created by TortoiseGit who has developed this product. In case you would like to…

Hi, @Martí Bastida Comas, thank you for reaching out to Atlassian Community. As you confirmed it works locally and by the error message you received, what could be happening is that your private docker registry could be behind a firewall and not allowing the pipeline to connect. If that’s the case, you would need to ensure…

Hi, @william, welcome to the community! I performed an analysis on our logs and confirmed that your email had a block on the server that prevented emails from being sent to you. This can occur when the system tries to send an email to the user and the account does not exist, is not activated yet, or rejects the email for…

Hi, Simon. Currently, Artifacts are not uploaded for failed steps. So, if you need that, we can create a feature request to implement it. We just need some additional details about your business case (the reason you need this feature) to raise this request. Kind regards, Caroline 

Hi, @Navakumar Krishnamoorthy, thank you for reaching out to Atlassian Community. In order to further investigate what's happening on your side, could you please share the following information with us? * Which browser are you using? Is it up to date? * Could you please test if it happens in an incognito window in Chrome?…

Hi, @Thomas Colpaert, welcome to the community! To give you some context around this behavior, this limit is set to prevent abuse, requiring us to validate if it's an actual person with a real need for that. I went ahead and exempted your workspace, so you should be able to create more than 300 repositories now. Please let…

Hi, @Sandeep Kumar, thank you for reaching out to Atlassian Community. Currently, user provisioning for Bitbucket Cloud from external sources such as Azure AD is not available. However, we do have this on our roadmap for FY23. In addition to this, we are tracking this feature here: *…

Hi, @PatricioSaldivar, welcome to Atlassian community! Just to give you some context around this behavior, this limit is set to prevent abuse, requiring us to validate if it's an actual person with a real need for that. I went ahead and exempted your workspace, so you should be able to create more than 300 repositories…

Hi, Patricio! My suggestion would be that you create a separate question for your issue, providing details on the errors you see and also whether it concerns a Bitbucket Cloud or Bitbucket Server repo. Kind regards, Caroline 

Hi, @aragsdale, Indeed, the problem is not solved yet, it seems to be an intermittent problem that is affecting a percentage of users. In this case, we have created a public bug: * https://jira.atlassian.com/browse/BCLOUD-21622 Our development team will post an update on the bug report when this is fixed. If you are not…

Hi, Revan! Thanks for your confirmation, I'm glad to know that! Kind regards, Caroline