youngmon/atlassian-qna huggingface dataset:
I'm not receiving invitation email
Asked by Daniel Asto:

My email is not receiving bitbucket invitation mail, maybe my email is blocked or bounced.


Answers:
author: Daniel Eads
body: Hey [@Daniel Asto](/t5/user/viewprofilepage/user-id/4989350) , welcome to the Community.

While email addresses can wind up blocked on the Atlassian side and need intervention, that doesn't seem to be the case with the email address you've used to post here to Community. I see some successful deliveries from our mail service to your email server a couple weeks ago. Nothing more recent than that was sent however.

I would suggest having the repo owner send the invitation again!

Alternatively, if the email address you used here doesn't match the email address that should be getting the invite, then we'd need to know at least the domain of the other email address to check our logs.

Cheers,  
Daniel \| Atlassian Team


author: Craig Castle-Mead
body: Assuming you've checked your spam/junk/any other email filtering - next steps I'd suggest:

1. Configure \*@bitbucket.org as an allowed sender
2. Ask your IT team to trace emails from \*@bitbucket.org

CCM

comments: author: Daniel Asto
body: 1 and 2 done, but I've read other trheads and they say bitbucket blocked or bounced their email addresses. I'd like to know how to get unblocked.


Tags: bitbucket-cloud

cloud
Bitbucket plugin license questions
Asked by cloudmanager135:

Hello.

Our Bitbucket license expired on January 31, 2022.

I want to use the updated Bitbucket Plugin in June 2022, Can't I use it?

The Bitbucket version is compatible with plugin.

There is a Bitbucket plug-in that I want to apply inside.

But I would be sad if i can't apply it for the above reasons.

Can I know if it's possible?


Answers:
author: Ulrich Kuhnhardt _IzymesCo_
body: Hello [@cloudmanager135](/t5/user/viewprofilepage/user-id/4989385) - welcome to the community!

Bitbucket server app licensing is implemented so that you can use _any_ app version that was released before or on the date your Bitbucket server license expires.

Unfortunately you can't use an app version that was released after the date your Bitbucket server license expired. However you should be able to create a trial license for the app.

Hope that helps.

Ulrich

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

comments: author: cloudmanager135
body: Thanks for response! [@Ulrich Kuhnhardt _IzymesCo_](/t5/user/viewprofilepage/user-id/4011392)

I can use the plugin of trial license, but I can't use the plugin of commercial license until update expired license. Is it true?

I'm so sad to hear that... Thanks!


author: Ulrich Kuhnhardt _IzymesCo_
body: Please allow me to rephrase:

1. If your Bitbucket server licence expired 31/Jan you can't upgrade to a version of **Bitbucket** that was released after 31/Jan

2. The same applies for plugin license. If your plugin license expired in June 22 you cannot use a version of the plugin that was released after June 22

I need to correct myself on what I said before: the app release date only matters w.r.t. the app license, not the Bitbucket license expiry date.

So in your case you can run a Bitbucket version released before 31/Jan/22 and run the app (if compatible with the Bitbucket version) on a version that's been released in or before Jun/22 if you have a commercial license valid till June 22


Tags: bitbucket-server

server
Is there a way to configure Required Approvers for a Pull Request?
Asked by Cole Orton:

Is there a way to configure Required Approvers for a Pull Request?

For example, our team wants us to have at least one person from the Required Approvers list approve a Pull Request before it can be merged.


Answers:
author: Sean Manwarring _Izymes_
body: Hi Cole!

Here are a few solutions;

1. In your Bitbucket Repository settings, you can create "Default Reviewers" on the left.

Then under "Branch Permissions" you can select "Check for at least N approval from default reviewers".

This will get you close, but not quite to the result you are after.

![Screen Shot 2022-07-19 at 11.40.55 am.png](https://community.atlassian.com/t5/image/serverpage/image-id/206634iC803EB67815D2E92/image-size/large?v=v2&px=999 "Screen Shot 2022-07-19 at 11.40.55 am.png")

2. You can sign up for bitbucket premium to block merge if N approvals from default reviewers have not been reached.

- You will need to change every bitbucket branch setting if a default reviewer leaves or you want to add a new one.

3. Our product [Workzone for Bitbucket](https://marketplace.atlassian.com/apps/1211303/workzone-pullrequest-workflow?hosting=cloud&tab=overview) will offer all of the above + more:

- Workzone will allow you to introduce reviewer [groups, group quota and merge-control.](https://www.izymes.com/docs/branch-configurations/)

- You can set up a default reviewer group, so you only need to change the group members and Workzone will apply that automatically.

Happy coding!

Sean

Technical Support at [Izymes](https://marketplace.atlassian.com/vendors/1210584/izymes-pty-ltd)

comments: author: Cole Orton
body: Hi Sean,

Thanks for your response!

For Options 1 and 2 I don't believe our version of BitBucket (Atlassian Bitbucket v7.17.5) supports those configurations.

In regards to Option 3, we're using Workzone 7.5.1. I was able to successfully configure Mandatory Users. However, the Pull Request Merge Check is all of those users to Approve. Is there a way where we can allow a specific number or ratio of those in the Mandatory Users list to Approve?

Thanks, Cole


author: Sean Manwarring _Izymes_
body: Hi Cole,

If you head to your repository settings \> "Workzone" (under "Add-Ons") \> "Merge" tab.

You can then edit the existing merge configuration you have set up or create one.

This will allow you to create a Boolean Expression based merge condition under the "**Advanced**" tab as seen in the screenshot below. This should solve your dilemma.

It may also help to refer to our new [documentation space here.](https://www.izymes.com/documentation/workzone-docs/workzone-feature-guide/)

Let me know how that goes \& if we can help with anything else.

Best, Sean  

![Screen Shot 2022-07-21 at 2.08.50 pm.png](https://community.atlassian.com/t5/image/serverpage/image-id/207157iB98DF897AACB0F91/image-size/large?v=v2&px=999 "Screen Shot 2022-07-21 at 2.08.50 pm.png")  


author: Cole Orton
body: That worked!

Thanks for your help on this.


Tags: atl-gruland

bitbucket-cloud

cloud
Windows Runner having problems with certain characters in paths
Asked by dkuerten:

I have setup a test project for building a .Net 6 application with a local Windows Runner setup on my machine.

The issue I found is that when the path where the runner is contains special characters (in my case ?/?/?) the runner fails to run to completion and reports probelms with *-File-Parameter*of the following scripts:

* tmp\\setupArtifacts{...}.ps1
* tmp\\setupCaches{...}.ps1
* tmp\\powershellScript{...}.ps1
* tmp\\powershellAfterScript{...}.ps1

The current solution is to move the runner to a path that does not contain special characters. In that case the pipeline runs without issues.

Here my yml:  

```
pipelines:
  custom:
    customPipelineWithRunnerAndCache:
       - step:
    name: Build and Test
    runs-on:
       - self.hosted
       - windows
    script:
       - cd TestApp
       - dotnet restore
       - dotnet build --no-restore --configuration Release
```


Answers:
author: Patrik S
body: Hello [@dkuerten](/t5/user/viewprofilepage/user-id/3194677) ,

Thank you for reaching out to Atlassian Community and reporting this issue!

I was able to simulate the same behavior on my end, so I went ahead and raised a bug for this in our public issue tracker. You can check the bug ticket at the following link :

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

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 t[his policy](https://confluence.atlassian.com/support/atlassian-cloud-bug-fix-policy-206865884.html) in mind.

Thank you, [@dkuerten](/t5/user/viewprofilepage/user-id/3194677) .

Kind regards,

Patrik S


Tags: bitbucket-pipelines

bitbucket-runners

cloud

windows
Avoid conflict for version file while using Automatic branch merging functionalities
Asked by vaibahv sharma:

Hi,

We want to use the "Automatic branch merging" for that we enabled the "Enable automatic branch merging" as mentioned at the page [Automatic branch merging.](https://confluence.atlassian.com/bitbucketserver0721/automatic-branch-merging-1115665735.html?utm_campaign=in-app-help&utm_medium=in-app-help&utm_source=stash)

Version: Atlassian Bitbucket v7.21.2

Now let's assume we have two branches **release/6.1** and **release/6.2** and both have version file. so each time there a PR merge in **release/6.1** code should auto merge to **release/6.1**.

But when we have different version let's say

**release/6.1**

Direct Commit 1\> version file content "6.1.1"

**release/6.2**

Direct Commit 1\> version file content "6.2.1"

Now made few change in **release/6.1** and made a **PR-1** from other **branch --\> release/6.1**

When I am merging this **PR-1** it is displaying message that it will merge to **release/6.2.** But when we hit the button merge instead of merging to **release/6.2** it always raise conflict **PR-2** from **release/6.1--\>release/6.2** for version file.

We tried this [suggestion](https://stackoverflow.com/questions/59289851/bitbucket-server-ignore-certain-files-during-auto-merge)

Followed:

* Login to your Bitbucket server via terminal.
* Execute `git config --global merge.ours.driver true`

And added below in .gitattribute

    version merge=ours

Faced the same issue.

Is there a way to avoid version file conflict as we don't want to merge version file from release/6.1 --\> release/6.2?


Answers:
author: vaibahv sharma
body: Could anyone reply on it?


Tags: bitbucket-server

git

server
Pull Request Validation
Asked by vinod lalwani:

Team,

I have been working on the bitbucket repo for a long time now and have been looking for PR Build validation to integrate with my pipelines exists on Azure DevOps.

Do we have any work-around or out-of-the-box feature where we can resolve this fix?

Problem Statement in detail -

Bitbucket is my code repo and the pipelines are on Azure DevOps. As soon as someone creates a PR - my pull-request pipeline gets triggered on ADO. I am looking for a solution where if my PR build gets failed, team should not have power to merge and complete the PR.

Did someone have faced this earlier? Please help!


Answers:
author: Patrik S
body: Hello [@vinod lalwani](/t5/user/viewprofilepage/user-id/4985789) ,

Welcome to Atlassian Community!

As long as your AzureDevOps builds are reporting their status back to Bitbucket, meaning that you can see the status of your Azure builds on the bitbucket pull requests page, you could leverage [Branch permissions](https://support.atlassian.com/bitbucket-cloud/docs/use-branch-permissions/) to prevent the PR from being merged if the build in the more recent commit has reported a failure.

Among other restrictions you can implement in your repository with branch permissions, one of them is to [suggest or require checks before a merge](https://support.atlassian.com/bitbucket-cloud/docs/suggest-or-require-checks-before-a-merge/), where you can suggest/enforce specific conditions on merges for individual branches or branch patterns. For your case, there's a specific merge check that would apply: **Check for {#} passed builds on the last commit and no failed builds.**This merge check will warn/prevent the user from merging the pull request if the last commit in the pull request has failed or has not met the required number of successful builds.

So in this case, you could [create a branch permission](https://support.atlassian.com/bitbucket-cloud/docs/use-branch-permissions/#Example-permissions-set-up) for the destination branch of your pull requests and enable the merge check above.

Please note that when you select any of these merge checks (and don't have the Premium plan), we'll just **warn** users when they have unresolved merge checks, but they'll still be able to merge. To prevent users from merging and enforce the completion of all merge checks you would have to upgrade to Premium and select **Prevent a merge with unresolved merge checks** . [Learn more about Premium.](https://support.atlassian.com/bitbucket-cloud/docs/bitbucket-cloud-premium-plan/)

Hope that helps! Let me know in case you have any questions.

Thank you, [@vinod lalwani](/t5/user/viewprofilepage/user-id/4985789) .

Kind regards,

Patrik S


Tags: bitbucket-cloud

cloud
Stopped receiving email notifications
Asked by Joao Jaime:

Like some other people already reported, I've stopped receiving email notifications.

Can you check what's going on please?

Thank you!


Answers:
author: Ben
body: Hey Joao,

I have checked our internal suppression list and cannot find your email listed here, I have also checked our SMTP logs and have verified that there are no SMTP bounce errors received from your mail server - however, no emails have been sent since 14/07/2022.

Can you please check your Personal Settings \> Notifications and ensure you are subscribed to notifications against repositories within your workspace?

If you are, the easiest way to trigger a notification email on that repository is to have someone @ mention you in a comment, if not please add and then test.

Cheers!

- Ben (Bitbucket Cloud Support)


Tags: bitbucket-cloud

cloud
Can I enable bitbucket pipelines for a specific branch without making a commit on master?
Asked by Dhairya Shah:

I am junior developer and I do not have access to make commits directly on master. I am working on cicd pipelines and I need to test it first on a feature branch before adding it to master. Is it possible to enable bitbucket pipelines only for feature branch by adding bitbucket-pipelines.yaml to that specific branch.


Answers:
author: Craig Nodwell
body: Hi [@Dhairya Shah](/t5/user/viewprofilepage/user-id/4988699) welcome to the community. You sure can. Have a review of this [document](https://support.atlassian.com/bitbucket-cloud/docs/configure-bitbucket-pipelinesyml/) for instruction.

comments: author: Craig Nodwell
body: Here's another [one](https://support.atlassian.com/bitbucket-cloud/docs/pipeline-triggers/) for you :)


Tags: bitbucket-cloud

bitbucket-pipelines

cloud
Container 'Build' exceeded memory limit nodejs
Asked by andy.tsoi:

Hi,

![Screenshot 2022-07-18 at 2.38.46 PM.png](/t5/image/serverpage/image-id/206426i87116C0360768069/image-dimensions/257x114?v=v2 "Screenshot 2022-07-18 at 2.38.46 PM.png")

I am trying to build and deploy my nextjs monorepo, I am not using any extra services and only the setting the default bit bucket docker's node image.

Why am i getting "Container 'Build' exceeded memory limit.", anyway the extend my build container memory?

\*\* my AppB is smaller app so it deployed with no problem, it just App A failed

below is my pipeline file:  
---

```
image: node:16.16.0

definitions:

  caches:

    yarn: /usr/local/share/.cache/yarn

    nodecustom: ./node_modules

    nextcacheAppA: ./dist/apps/appA/.next/cache

    nextcacheAppB: ./dist/apps/appB/.next/cache

pipelines:

  branches:

    master:

      - parallel:

        - step:

          size: 2x

          caches:

            - yarn

            - nodecustom

            - node

            - nextcacheshell

         name: Build and Deploy App A SIT

         deployment: SIT

         script:

           - yarn install --frozen-lockfile && export NETLIFY_SITE_ID=$SIT_SITE_ID && npx netlify deploy --build --prod --site $SIT_SITE_ID --auth $NETLIFY_AUTH_TOKEN

       - step:

          name: Build and Deploy App B SIT

          script:

            - yarn install --frozen-lockfile && export NETLIFY_SITE_ID=$APPB_SIT_SITE_ID && npx netlify deploy --build --prod --site $APPB_SIT_SITE_ID --auth $NETLIFY_AUTH_TOKEN
```


Answers:
author: Theodora Boudale
body: Hi [@andy_tsoi](/t5/user/viewprofilepage/user-id/4986744) and welcome to the community.

I see that you have created a support ticket for this issue, but I wanted to leave a reply here as well for any other users who may come across your post facing the same issue.

* Each step in a Pipelines build has 4 GB of memory available.
* If you use **size: 2x** for a step, like in the yml file you posted, this step will have 8 GB of memory available. This is the maximum supported in Pipelines builds. Please note that 2x pipelines will use twice the number of build minutes.  

* You can debug the build locally as per [this doc](https://support.atlassian.com/bitbucket-cloud/docs/debug-pipelines-locally-with-docker/) to check memory usage and see if you can configure your build to use less memory.
* Once you have set it up and the build is running locally, you can use the **docker stats** command (you need to run this in a separate window) and print the output to a file in a loop

```
while true; do date >> mem.txt && docker stats -a --no-stream >> mem.txt && sleep 2; done &
```

* If certain steps need more than 8 GB of memory, you can look into using [Runners](https://support.atlassian.com/bitbucket-cloud/docs/runners/) for these steps, as with Runners you can configure up to 32GB (8x) of memory.

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud
How can I define a rule to matching target branch name at pull-request section in yaml file?
Asked by QiangShen:

I have been read over <https://support.atlassian.com/bitbucket-cloud/docs/configure-bitbucket-pipelinesyml#pull-request> and <https://support.atlassian.com/bitbucket-cloud/docs/use-glob-patterns-on-the-pipelines-yaml-file/>  
All of this is talk about how to define glob patterns to matching "from branch" name , but I need to define a rule to match "target branch" name at pull-request section in yaml file.

Overall , I want scripts can work like this:

* when a pull request is **from branch** task/fix-404-bug to**target branch** relase/app-1.0.0:
  * match the pattern , do some scripts.
* when a pull request if **from branch** task/add-a-button to **target branch** feature/new-main-page
  * match pattern fail, don't do this scripts.

Can I do like this in yaml file ? Or it only just support to match from branch name?


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

I'm afraid that this is not possible at the moment, pull-requests definitions match the source branch only.

We have a feature request for what you are asking in our issue tracker:

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

Since you'd be interested in that, I would suggest adding your vote to that ticket (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.

In the meantime, you can check the workaround used by one of our other customers:

[https://jira.atlassian.com/browse/BCLOUD-17859?focusedCommentId=2651735\&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2651735](https://jira.atlassian.com/browse/BCLOUD-17859?focusedCommentId=2651735&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2651735)

You still need to determine the source branch in pull-requests, but during the build you can check the destination branch and fail the build if it doesn't match the desired branch(es).

Kind regards,  
Theodora

comments: author: QiangShen
body: Fully appreciate for you answer.

It just met all I want to know.

I will use the workaround for now.

Thanks Theodora!


author: Theodora Boudale
body: You are very welcome, please feel free to reach out if you ever need anything else!

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud

pull-request
How to set the width of a Client Side Extension column?
Asked by Johannes Heger:

Hello,

I'm updating a Bitbucket add-on to Bitbucket 8 and I'm using Client Side Extensions CSE the first time. I need a custom-column in pull-requests and can achieve this with the following code:

```
import {ButtonExtension} from '@atlassian/clientside-extensions';

/**
* @clientside-extension
* @extension-point bitbucket.ui.pullrequest.commits.table.column.after
*/
export default ButtonExtension.factory((pluginApi, context) => {
    // Visiblity depends per row, but for demo is always disabled.
    const isHidden = true;

    return {
        hidden: isHidden,
        header: 'My Header',
        iconBefore: 'page',
        label: 'My Label',
        className: 'my-class',
        onAction: () => {
        },
    };
});
```

This works, but the column is unexpectedly wide, it has a (implicit) width of 320px. I like to have the width set to 80px. Until now I haven't found any way to configure this statically in the CSE code or any CSS.

More background:

CSE renders the column always, but only if isHidden is false a DIV inside the TD is created. The className is set only to that DIV, but not for the empty TD nor the header TH, so creating a CSS like the following doesn't work:

```
/* Doesn't work: */
.my-class {
    width: 80px;
}
```

I can use a MutationObserver, but this results in a flicker.

My questions are:

1. How to set the width of a CSE-column statically?
2. Ans aside from that: Can I hide/show the CSE-column itself dynamically?

Kind regards,

Jo


Answers:
author: Christian Glockner
body: Hi Johannes,

Considering the nature of your question you may find someone who can help in our Developer Community at <https://community.developer.atlassian.com/>.

Cheers,

Christian

Premier Support Engineer

Atlassian

comments: author: Johannes Heger
body: Christian, thanks. I filed this questions again at <https://community.developer.atlassian.com/t/how-to-set-the-width-of-a-client-side-extension-column/59951>.


Tags: app

bitbucket-server

server
Folder link corrupted
Asked by rerosum:

After pushing my latest local changes to my remote/master branch, the "Spotify" folder shows up in the Bitbucket repo, however I can't click on it and drill down to see the files in the folder. The changes appear to have been pushed as 'git status' shows everything is up-to-date.

![A35CE0FE-18F8-4481-86B1-73E0C75C21B0.jpeg](/t5/image/serverpage/image-id/206383i961DF8497E27558A/image-size/large?v=v2&px=999 "A35CE0FE-18F8-4481-86B1-73E0C75C21B0.jpeg")


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

I can see that there is a commit hash next to the folder name, which indicates that this is a submodule.

**1** . Can you please confirm if you are using submodules?  
**2.** If so, does the repository for this submodule exist?  
**3.** Do you have a file named **.gitmodules** in the repo with the "Spotify" folder? If so, can you check the content of **.gitmodules** and see if the **path** and **url** for "Spotify" in that file are correct?

Kind regards,  
Theodora

comments: author: rerosum
body: Yes, it was a submodule issue that I created when copying folders around. I've cleaned things up and now everything looks good.

Thanks for the help!


author: Theodora Boudale
body: You are very welcome, I'm glad to hear that the issue is resolved now.

Please feel free to reach out if you ever need anything else!

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud