Caroline R Atlassian Team

Hi, @AWS Developer! Thank you for getting back to me and sharing the additional information. As per the teardown log, it looks like no file was uploaded as artifacts as there is no matching file. It searches for the files but doesn’t upload anything in the artifacts because it doesn’t find anything: Searching for files…

Hi, @ab36245! Thank you so much for sharing this information here, I really appreciate this. I confirmed this really is a bug and for this reason, I raised the following bug request to fix this issue: * https://jira.atlassian.com/browse/BCLOUD-21389 Our development team will post an update on the bug report when this is…

Hi, Juan! Thank you for the additional details. In fact, when you create a remote branch and run just a git pull, if you run git branch, you won't be able to see this branch on your repo. However, if you run git branch -r, you should be able to see this branch on the remote (-r will show you all the remote branches). So,…

Hi, Rohan! Welcome to the community! I performed an analysis on our logs and confirmed that your email was blocked on the server, that's why you weren't receiving this invitation. 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 email…

Hi, @Graeme Costin! Thank you for reaching out to Atlassian Community! You should be able to add this file using the same process you use to add and push your code. Could you confirm if you are facing any problems adding this file to your repository? Also, if this file is not a text document and it's a large file, I…

Hi, @AWS Developer! Welcome to the community! By the error message you shared in your description, it looks like the file you are trying to upload doesn’t exist - target/ContentProcessor-0.0.1-SNAPSHOT.jar Could you please verify that? You can first check if the file exists or not in the Update Lambda code step before…

Hi, Fatma! :) In this case, you need to add a section on your .yml file to run the pipelines on tags: tags: # add the 'tags' section release-*: # specify the tag - step: # define the build pipeline for the tag name: tags script: - echo $BITBUCKET_BUILD_NUMBER In the example above, all the tags that start with "release-"…

Hi, @ab36245! Welcome to the community! I reviewed the code you shared in your message and confirmed that it corresponds to the below error: ProjectPrivacyException: A repository in a private project cannot be publicly visible. So the repository you are trying to delete is set as public, but the project that has this…

Hi, @rhernandez! Welcome to the community! Currently, it’s not possible to download the audit logs via UI, but we have a script that can be used to scrape the logs from there, converting them to a .txt file. You can open the following link to access the script: *…

Hi, @Folke Byfors! Welcome to the community! Based on the details you shared with us, it seems that the PATH variable is the issue. Could you please check if you have set up the PATH variable as Workspace/Repository or deployment variable? As you can see in this documentation, if we configure a pipeline variable with the…

Hi, @Mahdi! I saw that you created a ticket with our support related to the same question, so to avoid any possible misunderstandings or miscommunication that may arise from discussing the same matter on two different platforms, let’s focus on the ticket instead. Once the ticket is resolved, feel free to share the…

Hi, @Gregory ANNE! Thank you for reaching out to Atlassian Community! Checking your image, I can see that its size is huge, so this is the reason that cache is not saved. Only caches under 1 GB once compressed are saved. For the cache to compress to under 1 GB, the size of the original images in the Docker must be < 2GB.…

Hi, Fatma! Could you confirm if you want to run the Pipeline on a Tag or would like to create a Tag? The reason I’m asking this is that in the original question, you asked to create a tag. If this is what you need, you can run the following: git tag $BITBUCKET_BUILD_NUMBER Looking forward to hearing from you. Kind regards,…

Hi, @Lokesh! Welcome to the community! Indeed, the author of the merge commit will be the user who created the Pull Request, as this person is considered the author of the work that is being merged on the PR. So, for this reason, when the PR is merged, that same user who authored the work will be shown as the Author.…

Hi, @BES1! Welcome to the community! I noticed that your Bitbucket account was created some days ago. In this case, could you confirm if you are using your regular password or an App password to log in to Visual Studio? The reason I'm asking this is that we announced in June that we are phasing out the use of user login…

Hi, Gabriel! Thanks for your confirmation! I'm glad to know everything is working now :) Kind regards, Caroline 

Hi, @Juan Martinez! Welcome to the community! In order to further investigate this case, could you please confirm the exact commands that you are using during this process, including how you are creating the branch? Also, instead of creating the branch locally and then pushing this to the remote repo, I understand you are…

Hi, @Gabriel Begueldo! Welcome to the community! I performed an analysis on our logs and confirmed that your email had a block on the server that prevented these 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 yet, is not activated, or it…

Hi, Willian! Thanks for your confirmation! I'm glad to know it worked! :) Kind regards, Caroline 

Hi, Victor! I'm glad to know this is resolved! :) Kind regards, Caroline

Hi, Will! Yes, this is the email that we removed the block. In order to test if you are receiving our emails, I have sent an invitation to one of my repositories to you and confirmed on our logs that this email left our servers. Could you confirm if you received my invitation? In case you still don't receive the…

You're welcome, Pavel! Kind regards, Caroline

Hi, @fatma.elbehi! Thank you for reaching out to Atlassian Community! Pipelines provides a set of default variables that are available for builds and can be used in scripts. It’s possible to get the build number by using the BITBUCKET_BUILD_NUMBER variable: The unique identifier for a build. It increments with each build…

Hi, @Willian Possa! 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 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…

Hi, @Pavel Bastov! Welcome to the community! It is possible to transfer Repository variables when transferring a repository to a different workspace. However, you will notice that after transferring the repo, the variables will disappear, but don’t worry, you just need to activate the Pipelines in this new repository after…

Hi, Patrick. Could you please try to create a new account with the email that was linked to your account? Please let me know how it goes. Kind regards, Caroline

Hi, @mbm! I'm glad to help :) Kind regards, Caroline 

Hi, @glenn_comiskey! Thank you for reaching out to Atlassian Community! Currently, Bitbucket Pipelines doesn't support variables for the Pipe name in the bitbucket-pipelines.yml file. However, we already have a feature request to add this option as you can see here: * https://jira.atlassian.com/browse/BCLOUD-20657…

Hi, @Roman Schepkin! Welcome to the community! It looks like you have defined a Repository variable name (process.env.URL) and you are trying to call a different variable name (process.env.NODE_ENV) in your code, is that correct? In order to troubleshoot the issue further, could you please share the following information…

Hi, @mntronslien! Thank you for reaching out to Atlassian Community! You are more than welcome to request our help here :) I confirmed you had 1 repository with a size of 3.7 GB, so I ran the GC against this repo and managed to reduce its size to 3.4 GB. Could you confirm if this is the local size? Also, I would like to…