youngmon/atlassian-qna huggingface dataset:
We are using atlassian integration for build and push the image to ecr repo
Asked by eks:

Hi Team,  
We are using Atlassian integration for build and push the image to ecr repo, but when we are build and push new image to ecr old image renaming as . (dot) , how to rename as any random version like 1.0.0, is it possible please suggest.

image: atlassian/pipelines-awscli

pipelines:  
branches:  
dev:  
- step:  
name: Build and Push Docker Image to the DEV ECR  
script:  
- docker build -t backend:latest .  
- pipe: atlassian/aws-ecr-push-image:2.2.0  
variables:  
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID  
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY  
AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION  
IMAGE_NAME: backend  
TAGS: 'latest'


Answers:
author: Igor Stoyanov
body: Hi [@eks](/t5/user/viewprofilepage/user-id/5386419) . Thanks for your question. This is [a normal behaviour](https://stackoverflow.com/a/74236040).  
To avoid this situation, just add additional tags besides \`latest\`. I.e.:

```
TAGS: 'my-tag latest'
```

So you will have an image tagged with two tags. After update (new image push), when \`latest\` tag will be moved to the new image, you will still have old image with \`my-tag\` tag.  

Regards, Igor  

comments: author: eks
body: Thanks for your answer Igor, If we are using like below it's not renaming the old image, and we need to maintain the image versioning why because if we want rollback last month image simply we can identify thorough and rollback and in this pipeline rollback also not clear, So could you please share the pipeline steps to maintain the image versioning and how to rollback?

TAGS: 'my-tag latest'

We have mentioned image tag is latest in fargate.json file while updating ECS Cluster through Atlassian integration it's pulling that image tag and updating, using image versioning we can update ecs cluster? please suggest this one also Thanks.


author: Igor Stoyanov
body: It is hard to understand your case, but i will try.  
How to push image with versions via pipe? Here you already mentioned how to build image:  
docker build -t backend:latest .  
Just add here version tag:  
docker build -t backend:latest -t backend:0.0.1 .  
Then push this image via pipe.  

So you push first image:

```
TAGS: '0.0.1 latest'
```

Now you have image on ecr with tags \`0.0.1\` and latest.  
Then you push second image:  
TAGS: '0.0.2 latest'  
Now you have two images on ecr. First with tag \`0.0.1\` and the second with tags \`0.0.2\` and latest. And so on. Now you have images on ECR with versions.  

Then you decide to rollback? It means you want to delete your last image or what? If answer is yes, then you should do it manually, because the pipe only pushes images.  

Additionally if you have struggle to use this pipe, you could implement your logic via the awscli, then provide here the example of logic you want. If some of the features are missing we will consider to add them to the pipe. If we decide to not include them you could always write your custom pipe with all your needs based on this pipe.  

Regards, Igor  


Tags: bitbucket-cloud

cloud
I'm trying to consume an API for branch restrictions here but I get this error
Asked by Jose Fernando Martinez:

Hello I am sending this thing for that API, ![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/296711iCF2CA1BD8852A97A/image-dimensions/458x138?v=v2 "image.png")

I have all headers good and all kind of authentications good but I get this error

{"type": "error", "error": {"message": "Something went wrong", "id": "9557509a980f4b00b77eb1623d7b1e5b"}}


Answers:
author: Theodora Boudale
body: Hi Jose Fernando and welcome to the community!

I see that the property "branch_match_kind" is missing from your call's data. This is necessary for the API call, and depending on its value you should use either "pattern" or "branch_type" but not both. Please allow me to explain:

If you want to create the branch restriction for the branch named development, your data should look like this:

```
{
"branch_match_kind": "glob",
"pattern": "development",
"kind": "require_approvals_to_merge",
"value": 2
}
```

If you want to create the branch restriction based on the repo's branching model and use the branch you set as **Development branch** from **Repository settings \> Branching model**, then your data should look like this:

```
{
"branch_match_kind": "branching_model",
"branch_type": "development",
"kind": "require_approvals_to_merge",
"value": 2
}
```

This second example will create a restriction for the branch defined as Development branch from from Repository settings \> Branching model, and if you change the Development branch from this page, then the branch restriction will be updated accordingly.

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

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud
Bitbucket pipeline docker memory issue.
Asked by manish_taazaa:

I have a bitbucket pipeline and there are many steps in pipeline , I am getting error of "docker memory exceed" as it is build trigger, I tried many combination of memory in the definition section of bitbucket pipeline but issue is not resolved. i can share my pipeline ,


Answers:
author: Patrik S
body: Hello [@manish_taazaa](/t5/user/viewprofilepage/user-id/5168033)

thank you for reaching out to Community!

Could you please confirm what exact error message you are receiving in the UI?

I ask this because the troubleshooting steps are different in cases where the **Build container** or the **Docker service container**is running out of memory.

The Build container is where your step's script is executed. The Docker service is where your docker commands (such as *docker build*) are executed.

We have the following troubleshooting guides for each of the cases that may be of help :

* [Scenario 2: Pipeline build failed with Container "Build" exceeded memory limit error](https://confluence.atlassian.com/bbkb/troubleshooting-bitbucket-pipelines-1141505226.html#TroubleshootingBitbucketPipelines-scenario2)
* [Scenario 12: Pipeline build failed with Container "Docker" exceeded memory limit error](https://confluence.atlassian.com/bbkb/troubleshooting-bitbucket-pipelines-1141505226.html#TroubleshootingBitbucketPipelines-scenario12)

If after following those instructions you are still receiving the error, we kindly ask you to share the exact error message and also the pipeline YAML so we can assist you further.

Thank you, [@manish_taazaa](/t5/user/viewprofilepage/user-id/5168033) !

Patrik S


Tags: bitbucket-cloud

bitbucket-pipelines

cloud

docker

error
Author name
Asked by Anchal Agarwal:

hello

I have 2 user AnchalGaruda and GarudaDevelopment.I have clone the repo using anchalgaruda and chnage the config with Garudadevelopment email id and now when i push the code it shows Garudadevelopment commited the code but code was commited by anchalgaruda

How to identify ho have push the code


Answers:
author: Patrik S
body: Hello [@Anchal Agarwal](/t5/user/viewprofilepage/user-id/4913085)

thank you for reaching out to Community!

The behavior you reported is actually how git was implemented. Commit and push are different operations. The commit is done locally, while the push sends your committed content to Bitbucket Cloud.

The user who signs the commits isn't necessarily the same user who authenticates the push. When you do a commit in your local machine, the author of the commit will be based on your local git settings. This is the author you will see in the commit list on the UI.

To configure the right commit author in your local machine you can follow the instructions in the article [Configure your DVCS username for commits](https://support.atlassian.com/bitbucket-cloud/docs/configure-your-dvcs-username-for-commits/)

Currently, it's not possible to see the user that authenticated the push directly in the UI, but we have the following feature request to include that information in the Audit Logs :

* <https://jira.atlassian.com/browse/BCLOUD-8322>

If you would be interested in that feature, we suggest adding your Vote to it as it helps our product managers to understand the interest. You can also add yourself as a watcher to be notified whenever there's any update on that feature.

Hope that helps! If you have any questions, feel free to ask!

Patrik S


Tags: bitbucket-cloud

cloud
User can't fork repository
Asked by Alex Rukhadze:

User can't fork repository. User is added into the project and repository with admin permission, forking is set to enable. but still retuns with the error shwon below  

![f7fbc25f-7b80-4a66-b968-68ef8fe7711b.png](https://community.atlassian.com/t5/image/serverpage/image-id/296629i6B47D8B850EF9DA3/image-size/large?v=v2&px=999 "f7fbc25f-7b80-4a66-b968-68ef8fe7711b.png")


Answers:
author: Patrik S
body: Hello [@Alex Rukhadze](/t5/user/viewprofilepage/user-id/5328492)

thank you for reaching out to Community!

When forking a repository you will be prompted to provide the destination workspace and project of the new repo (fork repo) that will be created. So besides having a fork enabled in the source repository, the user doing the fork also needs to have permission to create a new repo in the **destination project/workspace**.

Since the fork can be saved in a different project or even a different workspace, could you please confirm the user in question has **Admin** or **Create** access in the destination project and workspace?

To check that you can Navigate to the destination project in the UI \> select **Project Settings** \> **Project permissions** . Make sure the user has direct *Admin* or *Create* permission, or is part of a user group in the project that includes those permissions.

Thank you, [@Alex Rukhadze](/t5/user/viewprofilepage/user-id/5328492) !

Patrik S

comments: author: Alex Rukhadze
body: Hi Patrick,  
user has only admin permission in some projects and repositories, he is not a worksapce admin.  

He was trying to fork inside the project where he has admin permission.


author: Patrik S
body: Hello [@Alex Rukhadze](/t5/user/viewprofilepage/user-id/5328492) ,

thank you for the confirmation.

It seems you are being affected by a bug in the platform where having **admin** or **create**permission in the project is not allowing to fork a repository inside the project. This is being tracked in the following ticket on Bitbucket public issue tracker :

* <https://jira.atlassian.com/browse/BCLOUD-22884>

I would suggest you to add your vote there, since this helps both developers and product managers to understand the impact. Also, make sure you add yourself as a watcher in case you want to receive first-hand updates from that ticket. Please note that all bug fixes are implemented with [this policy](http://[https://confluence.atlassian.com/support/atlassian-cloud-bug-fix-policy-206865884.html]) in mind.

In the meantime, the user needs to be part of a group that has Admin permission in the workspace to be able to create the fork, or they can create the fork in a different workspace where they have admin permission.

Thank you, [@Alex Rukhadze](/t5/user/viewprofilepage/user-id/5328492) !

Patrik S


author: Alex Rukhadze
body: Thank you


author: Alex Rukhadze
body: \* update \* this was fork not a new repo


Tags: bitbucket-cloud

cloud
Renewed licensed not displayed on the local server
Asked by Federica Maria Piras:

We have recently renewed Jira and Bitbucket licenses and currently they are expiring on January 2024 but on our local server in both Jira and Bitbucket management pages there is a message "maintenance expires on January 19, 2023".

Is it safe to upgrade our Jira and Bitbucket softwares ?

The server is Ubuntu Linux 20.04, Jira software 9.4.1, Bitbucket 7.21.7

Thanks and regards.


Answers:
author: Christian Glockner
body: Hi Federica,

Did you update the license keys in Jira and Bitbucket Server with the new license codes you received after renewing?

<br />

Cheers,  
Christian  

Premier Support Engineer  
Atlassian

comments: author: Giulio Boni
body: Thank you, totally forgot about the license codes renewal. Now it works as expected.


author: Julius Davies _bit-booster_com_
body: To add to Christian's answer, as long as that banner is showing, it's not safe to upgrade to any versions of Jira ~~Data Center~~ Server or Bitbucket ~~Data Center~~ Server released on or after January 20th, 2023. (Edited on December 19th to remove my "Data Center" mistake).

After you upgrade both instances will go into a "read-only" mode and users will not be able to create new tickets or push new commits. After that point the "read-only" mode can only be unset by applying the license keys.

As Christian Glockner is suggesting, it sounds like the new license keys you recently purchased have not been correctly applied to your running instances.

p.s. Always take full backups before attempting to upgrade. Don't ask me why I say this. Painful memories...

comments: author: Giulio Boni
body: We use Jira Software, not Data Center, anyway thanks for the advice!


author: Julius Davies _bit-booster_com_
body: Oh yes, I forgot, Data Center versions go into "read-only mode" immediately upon expiry. It's only "Server" versions that give you a 1 year of maintenance, and let you stay on unmaintained versions after that 1 year.

(And probably why all "Server" versions will no longer receive any future updates after February 15th, 2024 !)


Tags: bitbucket-server

jira

jira-server

server
Is there a way to undo "Mark as spam"?
Asked by GW Kang:

I am using bitbucket cloud.  
I was editing an issue and accidentally clicked the "Mark as spam" button.  
I can no longer view this issue.  
Is there a way to undo "Mark as spam"?


Answers:
author: Patrik S
body: Hello [@GW Kang](/t5/user/viewprofilepage/user-id/5385268) and welcome to the Community!

By default when you navigate to the Issues page in a repository, the **Open** filter is applied, which makes the issues marked as spam to be filtered out.

However, you have the option to select the **All**filter, which will show all the issues in the repository, including the ones marked as spam.

![Screenshot 2023-12-14 at 11.56.16?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/296824iE4725DC647501BBB/image-size/large?v=v2&px=999 "Screenshot 2023-12-14 at 11.56.16?AM.png")

The issues marked as spam will be shown with a darker background, as in the example above.

To unflag the issue as Spam you can then open the issue, and click on the **More** button \> **Approve :**

**![Screenshot 2023-12-14 at 11.54.00?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/296825iB043BDCDFA8CD1AF/image-size/large?v=v2&px=999 "Screenshot 2023-12-14 at 11.54.00?AM.png")**

This will make the issue appear again when you navigate to the Issues page and the **Open** filter is applied.

If you want to see only issues marked as Spam, you can use the **Advanced search** option and create a filter for **Spam \> Is Spam \> Yes**. For your convenience, you can also use the direct link below, making sure to replace your workspace ID and repository :

* <https://bitbucket.org/>\<WORKSPACE\>/\<REPOSITORY\>/issues?is_spam=spam

That link will show only issues that were marked as Spam.

Hope that helps! If you have any questions feel free to ask.

Thank you, [@GW Kang](/t5/user/viewprofilepage/user-id/5385268) !  
Patrik S

comments: author: GW Kang
body: Thank you for your help with my question.

I was able to find the issue marked as spam again using the method you mentioned.

However, when I open the issue, I don't see any content or a 'More' button.

![scr.png](https://community.atlassian.com/t5/image/serverpage/image-id/296950iDB7DB7293C6BBA9E/image-size/large?v=v2&px=999 "scr.png")

<br />

It looks similar to when I open a link to an issue or repository for which I do not have permission.  
What problem do I have?

Thank you in advance.


author: Patrik S
body: Hello [@GW Kang](/t5/user/viewprofilepage/user-id/5385268) ,

You're seeing that page because only Admins of the repository can review issues marked as Spam. In this case, you can either ask the current owners of the workspace to grant you Admin permissions or ask a current admin to unmark that issue as spam.

Thank you, [@GW Kang](/t5/user/viewprofilepage/user-id/5385268) !

Patrik S


author: GW Kang
body: I solved the problem with your help.

Thank you very much.


author: Patrik S
body: You're very welcome!

Feel free to reach out to Community if you ever need help :)

Thank you [@GW Kang](/t5/user/viewprofilepage/user-id/5385268) !


Tags: bitbucket-cloud

cloud
Can not login to bitbucket.org (google account)
Asked by jingoong:

I can't log in to bitbucket.org with message as below.  

"You may run into this issue when you use specific browsers or add-ons that hide the referer header for id.atlassian.com and other Atlassian sites. Check for these and then try logging in again."

I'm using google account. Would you please check if my account is deactivated?


Answers:
author: jingoong
body: Sorry, I'll requet this issue to atlassian support.


Tags: bitbucket-cloud

cloud
Why doesn't "Git LFS Lock/Unlock" work ?
Asked by Artavazd:

I followed bitbucket document how to use LFS lock/unlock but I have the following error

<https://confluence.atlassian.com/bitbucketserver/working-with-git-lfs-files-970595880.html>   

git lfs lock \*BP_TestActorForLFSLockUnlock.uasset  
Locking \*BP_TestActorForLFSLockUnlock.uasset failed: Repository or object not found: <https://bitbucket.org/%7B%7D/%7B186ae863-5140-402d-a88a-1bfca6b8b064%7D/info/lfs/locks>  


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

I'm afraid that Git LFS Lock is not supported in Bitbucket Cloud at the moment. The documentation you shared here is for Bitbucket Server / Data Center, which is a product with a different codebase.

We have a feature request for what you are asking:

* <https://jira.atlassian.com/browse/BCLOUD-14454>

You can add your vote to that ticket (by selecting the **Vote for this issue** link) to express your interest. You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the **Start watching this issue** link) if you'd like to get notified via email on updates. Implementation of features is done as per our policy [here](https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html) and any updates will be posted in the feature request.

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud
I'm getting the error "We couldn?t log you in"
Asked by jingoong:

Hello, I have a account of Bitbucket but I'm getting the error as below  
"You may run into this issue when you use specific browsers or add-ons that hide the referer header for id.atlassian.com and other Atlassian sites. Check for these and then try logging in again. "  
Any help please.


Answers:
author: Sayed Bares [ServiceRocket]
body: [@jingoong](/t5/user/viewprofilepage/user-id/711042) can you try to login to your bitbucket in a different browser or incognito mode? and see if you can login

comments: author: jingoong
body: I'm using google account for login and in incognito mode also fails with same message.


author: Sayed Bares [ServiceRocket]
body: [@jingoong](/t5/user/viewprofilepage/user-id/711042) I suggest reaching out to [Atlassian support](https://support.atlassian.com/), according to [this thread](https://community.atlassian.com/t5/Bitbucket-questions/Unable-to-login-Bitbucket-We-couldn-t-log-you-in/qaq-p/1896018) your account might have been deactivated.


Tags: bitbucket-cloud

cloud
Unable to login Bitbucket
Asked by Alexander Muratov:

Hi,

I'm receiving error:

We couldn't log you in {#toc-hId--409614129}
--------------------------------------------

You may run into this issue when you use specific browsers or add-ons that hide the referer header for id.atlassian.com and other Atlassian sites. Check for these and then try logging in again.

Tried to clean caches but it didn't help. Could you please help me to login?


Answers:
author: Theodora Boudale
body: Hi Alexander and welcome to the community!

Your Bitbucket Cloud account's status was dormant, which is the reason for the error you were seeing.

I went ahead and reactivated it. Could you please check if you can log in now?

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud
Needs Info status
Asked by jason voegeli:

We often have a scenario during the PR code review process where someone does the review, but only has questions for the submitter. No changes are being requested. Only questions and they are finished with their review. They then mark the PR as Needs Work while waiting on answers to their questions, so that the PR drops to the bottom section of the PR summary list. If the submitter then responds to those questions without any new commits, the PR stays in Needs Work state and remains at the bottom of the PR summary list, and the reviewer isn't able to easily see that it's back in their court. Our project is large and we have a lot of users, so it's nearly impossible to monitor this effectively through email notifications. Is there any way to mark a PR as "needs info", where the submitter could then mark it as "info provided" after they have answered the questions, and then the reviewers would know it's ready for them again?


Answers:
author: Saxea _Flowie_
body: Hi [@jason voegeli](/t5/user/viewprofilepage/user-id/2191264)

You could implement this workflow using [Flowie labels set](https://flowie.app/docs/en/labels#labelset)(a Bitbucket addon we provide). You could, for instance, create a label "Status: Ready to review" and "Status: Info required" to reflect the status of the PRs.


Tags: bitbucket-server

server
404 Resource Not Found
Asked by Volcanica Game Labs LLP:

Got an invite for a repository. After accepting the invite I got a message that I am a part of this project now. But at the same time the page said 404 Resouce not found. I have two options to go from there, "previous screen" and "dashboard". Clicking on any of these links doesn't take me anywhere. Also, if I use this specific URL: "<https://bitbucket.org/account/workspaces>" it take me to a page where I can see the workspace that I was invited to. But clicking on it give the same 404 error. Infact clicking on any other button like, "Your work" , "Pull Requests" gives the same error.


Answers:
author: Theodora Boudale
body: Hi [@Volcanica Game Labs LLP](/t5/user/viewprofilepage/user-id/5384883) and welcome to the community!

I have reproduced this error when a user is invited to a user group that doesn't have access to any repos of that workspace. I created a bug report for this in our issue tracker: <https://jira.atlassian.com/browse/BCLOUD-23018>

Could you please ask the admin to check the permissions in the repo they want to invite you (from **Repository settings \> Repository permissions**) and see if the user group you were invited to is listed there? If it is not, the admin can add the user group to the repo, and you can then try to load the workspace page again.

Please feel free to let me know how it goes and if you still need assistance.

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud