Caroline R Atlassian Team

Hi, @Victor Tuzov! Welcome to the community! Just to give you some context around the users that appear in the notification, the first one is the user who has access to bitbucket and pushed the code to the remote repository. The second user is the author of the commit, so this information comes from your git configuration.…

Hi, @Chance Gehrke! Welcome to the community! Could you please try to use the following command to build the image? - docker build --build-arg SSH_PRIVATE_KEY . --file Dockerfile --tag ${IMAGE_NAME} I hope this helps, but do let me know if you have any questions. Kind regards, Caroline

Hi, @lprada! Thank you for reaching out to Atlassian Community! You can generate an artifact in a step by following the steps on this documentation. Once the artifact is generated, you can upload it using various methods as mentioned in the following links: * Deploy build artifacts to Bitbucket Downloads * Publish and link…

You're welcome, @Owais Aziz! I'm glad to help! :) Kind regards, Caroline

Hi, @Akarshit Verma! Welcome to the community! If you have the file name, you can run the following command to see the changes of this file even if the file was deleted: git log --full-history -- filename In case you would like to see just the last commit, which deleted the file, use -1 in the command above: git log…

Hi, @mbm! Thank you for reaching out to Atlassian Community! It looks like you're affected by a bug. This bug can occur intermittently, and our team is already looking into addressing it: * https://jira.atlassian.com/browse/BCLOUD-19548 As you have mentioned, as a workaround (while this problem is not fixed), you can push…

Hi, @Mach Dinh-Vu! Thanks for your confirmation, I'm glad to know it worked! Kind regards, Caroline

You are welcome, Francesco! Kind regards, Caroline

Hi, @Mach Dinh-Vu! Welcome to the community! A runner is a resource you provided to run your pipeline build and each runner is used for a step, hence when you have multiple steps or parallel steps it queues up because the resources are currently used by one of the steps. However, if you wish to run all the parallel steps…

Hi, @gotravelly! Welcome to the community! Thank you for reaching out to Atlassian Community! I ran the GC against your repository and we managed to reduce its size. Prior to proceeding with the next push to the remote repository, please make sure that all collaborators of the repository take a fresh clone of the repo from…

Hi, @Karthik Sarode! Welcome to the community! Could you please confirm if this is happening on Bitbucket Cloud? If so, could you check if you have whitelisted our IPs on the server where you have Jenkins? You can check our IP’s on our What are the IP addresses to configure a corporate firewall? documentation and, as you…

Hi, Francesco! I'm glad to help you! :) I ran the GC again and managed to reduce the size of these repositories to 1.5MB and 13MB. Kind regards, Caroline

Hi, @Francesco Torsello! Welcome to the community! I ran the GC against your repositories as requested to remove the dangling commits. To give you some context around the git GC process, Bitbucket triggers a garbage collection on the repository after each push, however aggressive GC is triggered by GIT once the…

Hi, @Thompson Lee! Currently, this is not possible, but I understand that this would be a great feature to implement, so I went ahead and created a feature request to our dev team: * https://jira.atlassian.com/browse/BCLOUD-21356 Right now, I would recommend that the users add a comment to inform the reviewers that the…

Hi, @Stijn Haezebrouck! Welcome to the community! I tested this on my side and this is working as expected for me. In this case, in order to further investigate what is happening in your repo, would it be possible for you to confirm to us: * What browser you are using and which version * Does the same issue occur in an…

Hi, @Robin Betts! Welcome to the community! I confirmed that the repository was still appearing on your repository list because the deletion process failed and the repo was stuck in 'Deleting' mode. In this case, I went ahead and removed this repo for you. About the other repository that is not appearing on your repo list,…

Hi, @Haoyu Zha! Welcome to the community! Currently, it’s not possible to configure the wait timeout for aws-ecs-deploy. In this case, I went ahead and created a feature request to add this option, as you can see here: * https://jira.atlassian.com/browse/BCLOUD-21351 I would suggest that you add your vote there (by…

Hi, @Danh Nguyen! Welcome to the community! Looks like you are affected by the bug where the Pipeline wizard no longer appears, we are already aware of this and currently tracking this bug at: * https://jira.atlassian.com/browse/BCLOUD-20669 Our development team will post an update on the bug report when this is fixed. If…

Hi, @Dan Engel! Welcome to the community! Currently, we do have an option to enforce the use of Jira Issue Keys on commit messages. In order to enable this feature, you can follow the next steps: * Open the repository you would like to change * Go to Repository Settings > Links * Enable the "Require issue keys in commit…

Hi, @Owais Aziz! Welcome to the community! I checked your Bitbucket account and confirmed you don’t have access to another workspace besides yours. In this case, in order to access your company's workspace, you need to ask one of the current admins of this workspace to invite you. They can add you to the admin group, this…

Hi, @Thompson Lee! Thank you for reaching out to Atlassian Community! Currently, there are 2 ways of receiving a notification when the assignee finishes the changes in a Pull Request: 1. You can change your notifications to receive an email every time someone makes a commit on the repository. In order to do that, you can…

Hi, @Aruna Virajith Chandrasekara! Welcome to the community! This is a workspace setting. If you set it to private, the workspace won't be visible to anyone who doesn't have explicit access to it. So, when someone who doesn't have access to this workspace tries to access it, they will see a page like this: However, if you…

Hi, @Enno! Welcome to the community! Before we start, I’d like to confirm that I've properly understood what is happening on your side. Feel free to correct me in case I have misunderstood something here. Apparently, when creating a new repository and adding a value to the "Default branch name" field, the repository is…

Hi, @Vibhanshu Biswas! Thank you for reaching out to Atlassian Community! Currently, Bitbucket UI doesn’t keep track of how many minutes were spent in the last months, as after being billed, this information is replaced by the current month's usage. At the moment, we do not have a report with the historic usage of build…

Hi, @IntuzCloud! Thank you for reaching out to Atlassian Community! Currently, this is not available on Bitbucket yet, you'll need to download the branches one by one. However, as you have several branches, we do understand that this option would improve your experience using Bitbucket, so I went ahead and created a…

Hi, @Elamkumaran! Thank you for reaching out to Atlassian Community! I'm afraid this is not possible in Bitbucket Cloud at this moment. We do have an import feature, but it will only import the repository itself, not the repository settings. However, we already have a feature request to add the ability to import the…

Hi, Paul, Thanks for getting back to me. In order to confirm that the repo was transferred to the new workspace or not, would you mind giving me the repository name with some "**"? For example: "media*****so**" This way, I can check it on our system and better understand what is happening here. Thank you! Kind regards,…

Hi, @JoeHz! Thank you for reaching out to Atlassian Community! I believe this issue is related to the following discussion at Stack Overflow post: * Debian 11 Update broke This issue has been raised with the owner of the image - Failing to build pipelines? #2, the owner of the issue mentioned that they are looking to fix…

Hi, Alain! Welcome to the community! We performed an analysis on our logs and confirmed that your email had a block on the server that prevented emails from being sent to this recipient. This can occur when the system tries to send an email to the user and the account does not exist yet, is not activated, or it rejects the…

Hi, @chandreddy! Welcome to the community! If you have administrative rights to this repository, you can change or transfer the ownership of the repository to another workspace. The transferred repository comes with its commit history and wiki, but it will lose the access groups and won’t inherit the destination account's…