youngmon/atlassian-qna huggingface dataset:
Where can I find the Bitbucket version specific upgrade notes for 7.x releases?
Asked by Rich Scire:

From the Bitbucket upgrade guide, the link to [Version specific upgrade notes](https://confluence.atlassian.com/bitbucketserver/bitbucket-server-upgrade-guide-776640551.html#BitbucketServerupgradeguide-n) just takes you back to the upgrade guide. Where can I find the upgrade notes? There's not link from the release notes and I can't find any reverence with Google.


Answers:
author: Kurt Klinner
body: [@Rich Scire](/t5/user/viewprofilepage/user-id/4468891)

Hi Richard

what exactly are you looking for, the general upgrade guidelines should cover all relevant actions, just in case a specific action would be needed for an upgrade you would get additional information.

Talk to you soon

Cheers

Kurt


Tags: bitbucket-server

data-center

server

upgrade
Required build checks with build statuses published from TeamCity
Asked by 8170605:

Hi,  

We've been testing the new required builds functionality and found out that it seemingly doesn't work out of the box in Bitbucket Data Center for build statuses published from TeamCity's Commit Status Publisher build feature.  

To configure the required build check in Bitbucket, a user is asked for a build key. We assumed that this is the value that is passed in the "key" field when commit statuses are published to Bitbucket. Yet it is seemingly not the case. At least the add required build form doesn't find any such keys (despite some statuses already published to various commits in our test repo) and if they key is added manually, Bitbucket claims that the merge operation is not allowed, even if a success status is published to the top commit in the respective branch.   

Could it be the case that some add-on on Bitbucket Data Center side is required? Or are these different kind of keys?


Answers:
author: Ulrich Kuhnhardt _IzymesCo_
body: The build result API for a certain commit as per REST API spec \[1\] can have the following payload:

###### Example {#toc-hId-190810582}

    {    "key": "TEST-REP123",    "state": "SUCCESSFUL",    "url": "https://bamboo.url/browse/TEST-REP1-3",    "buildNumber": "3",

The required build form lets you configure a merge-check based on successful build results for

* a specific target branch (or pattern)
* only consider build results with a certain 'key'

At runtime the build result will be recorded by Bitbucket and if there is a pull request with a source-ref hash identical to the the {commitId} and a matching build key the build result will be considered when checking if the PR can be merged, or should be blocked because of a failing build.

We at Izymes have made an add-on called [Workzone](https://marketplace.atlassian.com/apps/1211303/workzone-pullrequest-workflow?hosting=datacenter&tab=overview) that lets you specify the number of successful builds (usually 1) for a protected target branch and also triggers an automatic merge if the build was successful. We have found that for most teams a successful build is the last step in their PR merge process, and it's easy to automate. Trigger build, build pass, automatic merge, done.

I hope this helps your integration. Best, Ulrich

[Izymes](https://marketplace.atlassian.com/vendors/1210584/izymes-pty-ltd) - *Remove boring from work*

\[1\] <https://docs.atlassian.com/bitbucket-server/rest/7.17.0/bitbucket-rest.html#idp228>

comments: author: Ulrich Kuhnhardt _IzymesCo_
body: ... forgot to mention, Workzone does not require a 'build key' in its configuration for build result merge-checks and auto-merge.


Tags: bitbucket-server

server
What is the best process for Iterative Pull Requests (2nd or 3rd set of changes to peer review)
Asked by jdugasMT:

I am struggling to come up with a good and simple method of doing second pass and third pass peer reviews on pull requests.

I've come from an environment where we were using Crucible on our own server. Crucible had shortcomings for sure, but it handled iterative code reviews fairly well. I was able to see changes made between iterations of the code. With bitbucket I can look at all the individual commits after the first pass, but often times there are 3 or more commits after the initial review. Having to look at all these separately can be confusing when changes are undone/modifed on subsequent commits. Is there a good way to see the subsequent review commits combined without making multiple branches?

I'm hoping I'm just missing something in the features of BitBucket cloud.

thanks


Answers:
author: Caroline R
body: Hi, [@jdugasMT](/t5/user/viewprofilepage/user-id/613404)!

Thank you for reaching out to Atlassian Community!

Currently, we don't have Iterative Pull Requests in the Bitbucket cloud, but we already have a feature request to add this functionality:

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

However, we have a workaround that could help you see the changes introduced in e.g. the last 2 commits of the source branch, but **the diff will not take into account the master branch**. These are the steps you can follow to compare these commits:

* Go to the **Source** page of the repo \> select the 3 dots from the upper right corner;

* Open **Compare branches or tags;**

* In the dropdowns of the Compare page, enter the commit hash you would like to compare;

* Click on Compare.

  * **This diff will only show the changes introduced between these 2 commits.**

Also, I would suggest that you add your vote in the feature request that I mentioned above (by selecting the **Vote for this issue** link) as the number of votes helps the development team and product managers better understand the demand for new features.

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 new 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.

I hope this helps, but do let me know if you have any questions.

Kind regards,  
Caroline

comments: author: jdugasMT
body: Thank you. I voted on BCLOUD-14889 and made my peers aware of it.

I was not aware that I could put commit hashes into the compare destination/source fields. That is a reasonable workaround for the time being.


author: Caroline R
body: Hi, [@jdugasMT](/t5/user/viewprofilepage/user-id/613404)!

I'm glad to know the workaround will be useful to you and your team.


Tags: bitbucket-cloud

cloud
User not receiving invitation email.
Asked by poconnor3:

User \<email removed due to privacy reasons\> is not receiving an invitation email. I assume there was a hard bounce. Is there a way to remove the block outside of this forum?


Answers:
author: Caroline R
body: Hi, [@poconnor3](/t5/user/viewprofilepage/user-id/3341857)!

Thank you for reaching out to Atlassian Community!

Indeed, this email had a block on the server. 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 for some internal reason.

In this case, I have removed the block from this email. Could you please **remove** the invitation and send them a new one? You can do this by following the next steps:

In case you have invited them to a **specific repository**:

* Access the workspace \> Go to the repo you have invited them to;

* Access the **Repository Settings** \> **User and group access;**

* Click on the "invitation pending";

* Select the "**Cancel invitation**" option to remove the invitation;

* Add the email again to send a new invitation.

In case you have invited them to a **group on this workspace**:

* Access the workspace \> **Settings**;

* Access **User groups** \> Open the group you have invited them to**;**

* Click on the "invitation pending";

* Select the "Cancel invitation" option to remove the invitation;

* Add the email again to send a new invitation.

Please let me know how it goes and feel free to share any additional questions or concerns regarding this case.

Answering your last question:  
> Is there a way to remove the block outside of this forum?

You can either add a question here or create a ticket with us through the following link:

* <https://support.atlassian.com/contact/>
* Select Technical issues and bugs
* Product: Bitbucket
* Inform the workspace URL
* In the "Are you having an issue with Bitbucket workspace invitations?" option, select yes

Kind regards,  
Caroline


Tags: bitbucket-cloud

cloud
Exclude folders in the upload step of aws-code-deploy
Asked by rickhaasteren:

I'm using the aws-code-deploy to deploy my code to AWS. I have various folders in my repo that I don't need in the upload stel (like .git, src and tests).

I noticed that the aws-s3-deploy pipe has the option to exclude certain folders using the EXTRA ARGS parameter, for instance like this:

EXTRA_ARGS: '--exclude=.git/\* --exclude=src/\* --exclude=tests/\*

However, this doesn't seem to work for aws-code-deploy. Is there another way to exclude folders and files in the upload step?


Answers:
author: Rick van Haasteren
body: The solution turned out to be excluding the folders in the zip command. Here's what I'm running now:

```
- step:
    name: Build
    script:
      - cd app/../ && zip -r myapp.zip  * .[^.]* -x 'tests/*' -x 'src/*'  -x '.git/*'   -x 'gulp/*'
    artifacts:
      - myapp.zip
```

This excludes the tests, src, gulp and .git folders.


author: Igor Stoyanov
body: [@rickhaasteren](/t5/user/viewprofilepage/user-id/4623048) hi. Thanks for your question.  

I did not found [here](https://docs.aws.amazon.com/codedeploy/latest/APIReference/API_CreateDeployment.html) how to exclude some folders from deploy. So i doubt we can implement such feature in aws-code-deploy pipe. Keep in mind that EXTRA_ARGS in aws-s3-deploy and aws-code-deploy are not the same variables.

After some investigation i found [this article](https://stackoverflow.com/questions/43959771/is-there-a-way-to-exclude-a-directory-in-aws-codedeploy). Maybe it can help you.

Also when you do upload with aws-code-deploy you can provide needed ZIP_FILE (with excluded directories) before you do deploy with aws-code-deploy.

Regards, Igor


Tags: aws

aws-codedeploy

bitbucket-pipelines

cloud
Is it possible to check merge type of already merged PRs?
Asked by Dominik Panas:

Hello

Is it possible to check merge type of already merged PRs?


Answers:
author: Caroline R
body: Hi, [@Dominik Panas](/t5/user/viewprofilepage/user-id/2647094)!

Thank you for reaching out to Atlassian Community!

Currently, it's not possible to see the merge strategy of merged Pull Requests in Bitbucket Cloud, we can only see how the history of commits looks like. In this case, I went ahead and created a feature request to implement this on Bitbucket Cloud:

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

I would suggest that you add your vote there (by selecting the **Vote for this issue** link) as the number of votes helps the development team and product managers better understand the demand for new features.

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 new 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,  
Caroline


Tags: bitbucket-cloud

cloud
how can i set clone permissions
Asked by GodSvarog:

hello everybody.

i need my employees to make only:

```
git clone --branch=first --depth=1 https://GodSvarog@bitbucket.org/Alex_Svar/sandbox.git
```

but not

```
git clone https://GodSvarog@bitbucket.org/Alex_Svar/sandbox.git?
```

how can i set permissions on clone operations for my employees?


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

I'm afraid that it is not possible to enforce this. If a user has at least read access to a repository, they get access to all branches and they can clone either the entire repo or a certain branch only.

You can prevent certain users from pushing to certain branches with [branch permissions](https://support.atlassian.com/bitbucket-cloud/docs/use-branch-permissions/), but it is not possible to enforce what type of clone they will make.

Kind regards,  
Theodora

comments: author: GodSvarog
body: i thank you for reply.

i had already found a solution. i need just to make other repository and push to it necessary branch.


author: Theodora Boudale
body: Thank you for the update, I'm glad you found a way around this.


Tags: bitbucket-cloud

cloud
[AWS ECS deploy] Support for patching task definitions
Asked by Krzysztof Siersze?:

It would be a nice feature if one could provide a patch for an existing task definition rather than complete JSON in AWS ECS pipe's\`TASK_DEFINITION\`.

A valid use case would be to bump the Docker image version for a container definition of a task without touching anything else. I guess one could easily find other use cases, though.

Such a feature could be implemented in the form of a \`TASK_DEFINITON_MODE=patch\|overwrite' flag, with the implementation for \`patch\` being sth like

```
TASK_DEFINITION=`aws ecs describe-task-definition --task-definition ${name} | json-patch -p ${TASK_DEFINITION}`
```


Answers:
author: Oleksandr Kyrdan
body: Hi [@Krzysztof Siersze?](/t5/user/viewprofilepage/user-id/4378335)

Thank your for your question!

It could be your case to use FORCE_NEW_DEPLOYMENT variable:
> Whether to force a new deployment of the service. Default: `false`. Use this option if you need to trigger a new deployment with no service definition changes: if your updated Docker image uses the same tag as what is in the existing task definition for your service (for example, my_image:latest ).

```
script:  - pipe: atlassian/aws-ecs-deploy:1.11.0    variables:      AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID      AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY      AWS_DEFAULT_REGION: 'us-east-1'      CLUSTER_NAME: 'my-ecs-cluster'      SERVICE_NAME: 'my-ecs-service'      FORCE_NEW_DEPLOYMENT: 'true'
```

related question [Deploy to AWS ECS without Task Defintion](https://community.atlassian.com/t5/Bitbucket-questions/Deploy-to-AWS-ECS-without-Task-Defintion/qaq-p/1580401).  

Best regards,  
Oleksandr Kyrdan


author: Igor Stoyanov
body: [@Krzysztof Siersze?](/t5/user/viewprofilepage/user-id/4378335) hi. Thanks for your idea. We will investigate about that and notify you if this feature becomes available.

Regards, Igor


Tags: aws

bitbucket-pipelines

cloud
Get list of repositories using the deprecated Services?
Asked by thomthom:

I got an email announcing an deprecation:
> We noticed you are an admin for a Bitbucket Cloud repository that is still utilizing our original Services feature. We had previously announced that we will end support for this feature and recommended migrating repositories to Bitbucket webhooks.

I have quote a few repositories, and I have no idea which is affected. Is there any way to obtain a list of affected repositories?


Answers:
author: Yana
body: Hi there,

You can see additional details on this community post:

<https://community.atlassian.com/t5/Bitbucket-articles/Email-about-ending-Bitbucket-Services-feature/ba-p/1853515>

Our team is working on a change that will make is easier for repository Admins to identify those in Bitbucket UI, the change should be deployed by end of day on November 4. We will share an update on the community thread above shortly.

However in the mean time, you can reach out to support to get the list of repositories.

<https://support.atlassian.com/contact/#/>

Thank you.

Yana

comments: author: thomthom
body: Thank you for the feedback. I see that thread mention an API to call to get a list. But you also mention a UI that was deployed on November 4th? Where can I find that UI?


author: Yana
body: Hi [@thomthom](/t5/user/viewprofilepage/user-id/664833)

As mentioned the community thread listed above, in order to see if a repository has Services configured, you can follow these steps:

Currently, repository **admins** can determine what **Services** are enabled on a repository by doing the following:

1. Navigate to the repository
2. From there, find and select **Repository settings** on the left-hand navigation bar
3. In **Repository settings** , on the left-hand navigation bar, under **Workflow,** you should see a **Services** page. Click it. If you do not see a **Services** page then that means you do not have any services enabled on the repository.
4. Once the page has loaded you should see the **Services** the repo has

This is only helpful if you have fewer repositories, for users with large number of repositories you will need to use the API call that our engineers shared on the post.

Hope this helps, do let us know if we can help further.

Yana


Tags: bitbucket-cloud

cloud
JIRA Issue Key not working when I try to push a code to Bitcuket
Asked by Casey Moeslein:

Hi,

I currently use IntelliJ to push my code to Bitbucket. I am required to put a JIRA Issue Key in the comments section when I push my code.

For some reason, when I include both the JIRA issue key and link I get this error message:

remote: Please follow the instructions to amend your commit(s).  
remote: Checking for Jira key in this instance:  
remote: Jira URL is empty in hook configuration. Please update it to the correct Jira instance.

Any suggestions on how to fix this?


Answers:
author: Theodora Boudale
body: Hi Casey,

Are you using Bitbucket Cloud (<https://bitbucket.org/>) or Bitbucket Server (self-hosted instance)? I'm asking because the two products are different.

I see that your question has the tag 'bitbucket-cloud', but I cannot find any Bitbucket Cloud account with the same email as your community account in our system, so I just wanted to get clarification first on which product you are using.

Could you also please let us know if the Jira instance in question is a Cloud or Server one?

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud
Connect to Circle Ci fails
Asked by Alexandre:

Hi there,

I'm having troubles connecting BitBucket to CircleCi:

* On CircleCi, I click Connect in my account integrations
* I get the error "The identity provided by your VCS service is already associated with a different account. Please try logging in using that account or contact us for further help."
* On my BitBucket account, I can see in the App Authorizations a line for Circle CI

But I cannot see pipeline info in CircleCI from my BitBucket PR.

Has anyone already encountered this issue?

Thanks


Answers:
author: Syahrul
body: Hi [@Alexandre](/t5/user/viewprofilepage/user-id/4622241)

Welcome to the community!

The error indicates that you already have an existing integration installed between CircleCI and Bitbucket, I would suggest checking with your team if anyone already has installed the integration previously as it may cause conflict.  

Once verified, re-install the integration using an admin account on both CircleCI and Bitbucket to avoid permission issues.

If you still have an issue viewing the build status in your Pull request after re-installing the integration please get back to me so we can troubleshoot the issue further.

Cheers,  
Syahrul

comments: author: Alexandre
body: Hi [@Syahrul](/t5/user/viewprofilepage/user-id/744536)

Thanks for your response! I had already done those checks.

CircleCi happened to have a problem on my account. My admin contacted their support and they could remove the issue.

Cheers,

Alexandre


Tags: bitbucket-cloud

circle-ci

cloud
In Bitbucket cloud - Is it possible to see both Author and Committer on a commit?
Asked by Jarle Jacobsen:

Given this situation:

* User A commits change 123 to a branch BA
* User B cherry pics the 123 commit to branch BB creating commit 456

In the BB branch the commit is shown with Author A only, is it possible to see Committer B somewhere? If I open the 456 commit it states *A committed 456*. This is not correct B committed, and A was the Author.


Answers:
author: Jarle Jacobsen
body: Never mind. Found this issue [BCLOUD-13836](https://jira.atlassian.com/browse/BCLOUD-13836)


Tags: bitbucket-cloud

cloud
Can't use kubectl patch using atlassian/azure-aks-deploy
Asked by heldersatin:

Hello everyone,

I'm trying to use a kubectl patch command to update a deployment by changing a metadata label on my deployment, the command i'm using is this one:  

kubectl patch deployment my-deployment -n my-namespace -p '{\\"spec\\":{\\"template\\":{\\"metadata\\":{\\"labels\\":{\\"redeploy\\":\\"55\\"}}}}}'  

When running it on power shell it works perfectly but when i add it to my pipeline i get all sorts of errors, currently my step is as follows:

- pipe: atlassian/azure-aks-deploy:1.0.2  
variables:  
AZURE_APP_ID: $AZURE_APP_ID  
AZURE_PASSWORD: $AZURE_PASSWORD  
AZURE_TENANT_ID: $AZURE_TENANT_ID  
AZURE_AKS_NAME: $AKS_CLUSTER_NAME  
AZURE_RESOURCE_GROUP: $AKS_RESOURCE_GROUP  
KUBECTL_COMMAND: 'patch deployment my-deployment'  
KUBECTL_ARGUMENTS: '-n my-namespace -p ''{\\\\"spec\\\\":{\\\\"template\\\\":{\\\\"metadata\\\\":{\\\\"labels\\\\":{\\\\"redeploy\\\\":\\\\"$BITBUCKET_BUILD_NUMBER\\\\"}}}}}'''  

But the output of the pipeline is  
INFO: running kubectl command patch deployment my-deployment using generic handler  
kubectl patch deployment my-deployment -n my-namespace -p '{\"spec\":{\"template\":{\"metadata\":{\"labels\":{\"redeploy\":\"55\"}}}}}'  
Error from server (BadRequest): json: cannot unmarshal string into Go value of type map[string]interface {}  
I've tried scaping that string in all sorts of ways but nothing works, even tried using the yaml style for the patch command with the same outcome. Is there something obvious i'm missing here?


Answers:
author: heldersatin
body: Answering my own question, it seems that the kubectl version being using a little far behind the current version, so the correct syntax was:

- pipe: atlassian/azure-aks-deploy:1.0.2  
variables:  
AZURE_APP_ID: $AZURE_APP_ID  
AZURE_PASSWORD: $AZURE_PASSWORD  
AZURE_TENANT_ID: $AZURE_TENANT_ID  
AZURE_AKS_NAME: $AKS_CLUSTER_NAME  
AZURE_RESOURCE_GROUP: $AKS_RESOURCE_GROUP  
KUBECTL_COMMAND: 'patch deployment my-deployment'  
KUBECTL_ARGUMENTS: '-n my-namespace -p {"spec":{"template":{"metadata":{"labels":{"redeploy":"$BITBUCKET_BUILD_NUMBER"}}}}}'  

Just had to remove the backslashes and the extra single quotes that marked the patch string


Tags: azure

bitbucket-cloud

bitbucket-pipelines

kubernetes
Cloud - Project Level Branch Permissions
Asked by Bunny Davies:

We're looking to set branch permissions at the project level for all child repos.

According to the following article it can be done with Bitbucket Data Center and Server, but I can't see any documention or options for doing the same in Bitbucket Cloud.

<https://confluence.atlassian.com/bitbucketserver/using-branch-permissions-776639807.html>

Is that a Data Center/Service product only feature? If it's not natively supported for Bitbucket Cloud in the web interface, is there another way of going about setting branch permissions en masse?

Many thanks.


Answers:
author: Theodora Boudale
body: Hi [@Bunny Davies](/t5/user/viewprofilepage/user-id/4621811),

This feature is indeed available in Bitbucket Server/Data Center only, it is not available in Cloud yet. We have a feature request about this in our issue tracker that I would suggest voting for if you'd be interested in this:

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

We have an API endpoint for creating branch permissions:

* <https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/branch-restrictions#post>

So, you could write a script that creates the same branch permissions for the repositories you like.

If you have any questions, please feel free to let me know.

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud