youngmon/atlassian-qna huggingface dataset:
After upgradation Bibucket repository showing offine
Asked by jiqbal.c:

2024-02-16 17:19:39,200 DEBUG \[mesh-grpc-request:thread-3\] c.a.s.i.scm.git.mesh.MeshChannel Sidecar#0 (<http://localhost:7777>): Connectivity state updated t  
o TRANSIENT_FAILURE  
2024-02-16 17:19:39,206 DEBUG \[spring-startup\] c.a.s.i.i18n.PluginI18nService No values found in any valid locale for key bitbucket.service.mesh.node.unava  
ilable and locales \[en_US, en\]  
2024-02-16 17:19:39,206 DEBUG \[spring-startup\] c.a.s.i.i18n.PluginI18nService No values found in any valid locale for key bitbucket.service.mesh.node.unava  
ilable and locales \[en_US, en\]  
2024-02-16 17:19:39,206 ERROR \[spring-startup\] c.a.s.i.mesh.DefaultMeshController Failed to configure sidecar on initialization  
com.atlassian.stash.internal.mesh.SidecarUnavailableException: Sidecar is currently unavailable  
at com.atlassian.stash.internal.mesh.DefaultMeshController.maybeConfigureSidecar(DefaultMeshController.java:276)  
at com.atlassian.stash.internal.mesh.DefaultMeshController.lambda$maybeConfigureSidecar$3(DefaultMeshController.java:266)  
at java.base/java.util.Optional.ifPresent(Optional.java:178)


Answers:
author: Aman Shrivastava
body: Hi jiqbal_c,

From the stack trace, It appears that the Mesh sidecar process, which is a child process of Bitbucket's main process, is not starting. As of Bitbucket 8.X and later versions, all repository interactions take place through the mesh process, and if it doesn't start or crash in the middle, an error "Repository not available - offline" appears.

I suggest you review the KB [Error "Repository not available - offline" occurs when accessing a repository in Bitbucket Server](https://confluence.atlassian.com/bitbucketserverkb/error-repository-not-available-offline-occurs-when-accessing-a-repository-in-bitbucket-server-1155145973.html) and if it doesn't resolve your problem please raise a ticket with [Atlassian support](https://support.atlassian.com) to check the underlying cause of the issue.  

Regards,  
Aman

comments: author: jiqbal.c
body: Thanks. the issue issue resolved, when i make the entries of servername \& IP's inside the server /etc/hosts file. and removed 127.0.0.1 localhost entry.


author: DenJr
body: Hello, I have the same issue. Could you please provide more details about your solution? I changed the `/etc/hosts` file and specified the IP address of the server and its servername instead of `127.0.0.1 localhost`, but it did not solve my problem.


author: jiqbal.c
body: whats your bitbucket and version and can you please share the error message.


Tags: server
Notification Order for Pull Requests reviewers
Asked by Daniel Lutz:

Hey community,

does it exist a way to change to order of notifcations when a pull reuest is created?

When we open a pull request and add a reviewer the person is instantly notified. Is there a way to change this behaviour after all corresponding check pipelines which run there are completet and green? Background of the case is when the pull request pipeline failed (build error or test error) the reviewer can wait until th problem ist fixed.

Best regards

Daniel


Answers:
author: Ulrich Kuhnhardt _IzymesCo_
body: Hello Daniel,

Welcome to the community!

It's great to see how Bitbucket apps are providing important features that are still missing in Bitbucket cloud.

I understand that you *only* want to notify reviewers if the source branch of the PR has a successful build result (via pipeline), because there's no point reviewing a PR when the pipeline is failing.

We are addressing this issue with our app [Workzone for Bitbucket](https://marketplace.atlassian.com/apps/1211303/workzone-pullrequest-workflow?tab=overview&hosting=cloud) (cloud), it will be able to cater to your needs.  
[Here is a link to Workzone's documentation space](https://izymes.com/docs/reviewer-and-approval-configuration/#:~:text=(2)%20Only%20after%20successful%20build%20(optional)%3A%20Some%20workflows%20require%20a%20successful%20build%20for%20the%20pull%20request%20source%20branch%20before%20the%20review%20starts.%20If%20this%20is%20checked%20Workzone%20will%20not%20add%20reviewers%20to%20a%20pull%20request%20until%20a%20successful%20build%20is%20detected.) highlighting how to create a configuration that adds reviewers only after a successful build, i.e. also allowing them to only receive the notification after a successful build.

<br />

Hopefully, that solves your problem!

Happy Coding,

Ulrich

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


author: Saxea _Flowie_
body: Hi [@Daniel Lutz](/t5/user/viewprofilepage/user-id/5311730)

Currently not possible. I think the closest you could get to this is by adding the reviewers after the pipelines succeed using the Bitbucket API.

The good news is that this is on our radar for [Flowie](https://flowie.app/) since it has been requested already, and we should support it via Flowie in the near future. If you get in touch via our website, we can notify you when it's available!

comments: author: Daniel Lutz
body: Thank you for answering. Okay i wil take a look on Flowie and WorkZone and the possibilities of the Bitbucket API.

Best regards

Daniel


Tags: bitbucket-cloud

cloud
Composer failing in pipeline but not when manually run
Asked by Mike Holzer:

I am running a Drupal deployment and as part of the build, I have composer pull in dependencies. Since I upgraded to the latest version of Drupal in September, our pipeline has been failing due to a dependency issue. When we run our pipeline manually or (or even just running composer locally), we don't have the dependency issue.

Is there any way to debug what is going on in the pipeline vs our devs' local environments?


Answers:
author: Theodora Boudale
body: Hi Mike,

Do your Pipelines builds run on Atlassian's infrastructure or are you using one of our [self-hosted runners](https://support.atlassian.com/bitbucket-cloud/docs/runners/)?

If the pipelines builds run on Atlassian's infrastructure or with a self-hosted Linux Docker runner, they use Docker containers. For every step of your build, a Docker container starts (the build container) using the image you have specified in your bitbucket-pipelines.yml file. The repo is cloned in the build container, and then the commands of the step's script are executed. When the step finishes that Docker container gets destroyed.

Builds running with self-hosted Linux Shell, MacOS or Windows Runner run directly on the host machine using Bash (for Linux Shell and MacOS runners) and PowerShell (for Windows runners).

It is not possible to debug the build in Pipelines while it is running. You could debug by adding some additional commands in your yml file to run with the next build.

We have the following guide for debugging a build locally with Docker. This is useful if you want to debug a build running on Atlassian's infrastructure or with a self-hosted Linux Docker runner.

* <https://confluence.atlassian.com/bbkb/troubleshoot-failed-bitbucket-pipelines-locally-with-docker-1318882094.html>

You can try this to see if your build also fails when you debug locally with Docker or if it is successful.

You mentioned that when you run your pipeline manually you don't have this issue, so we would need to see what is different between these two builds.

Does the automated pipeline that fails run on the default, branches, pull-requests, or tags definition?

When you run it manually, do you trigger the pipeline for the same branch/commit as the automated build? And are you selecting the same pipeline definition that failed in the automated run?

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud

composer
App password revoked by me, can old user still pull or push repo ?
Asked by Fritware Solutions Private Limited:

I am admin of company previously some developer works on my project, now I have revoked app password and created new one. Can old user access my repo or full and push ?


Answers:
author: Ben
body: Hi @\[deleted\] !

Welcome to the Bitbucket Cloud community! :)

As soon as the app password is revoked, the user will not be able to use it to authenticate to your repository over HTTPS, this includes push/pull/clone operations.

I would suggest ensuring that if you do not wish for someone to access repositories, that you check **Workspace Settings \> User Directory** and review the users that are members on your workspace and remove them if necessary.

Cheers!

- Ben (Bitbucket Cloud Support)


Tags: bitbucket-cloud

cloud
Can a Server-side hook be utilized to update the appropriate Jira Issue IDs for a commit?
Asked by Samir Kabiraj:

Is it possible to utilize any of the server-side hooks to validate and only link the validated Jira Issues to the commit?  
As Bitbucket and Jira integrations is done strictly based on commit messages it is possible to enter multiple existing Jira Issues IDs in one commit message. Now that may seem to be valid from the developer's perspective as the same commit may be related to more than one Jira Issues. But that also opens the possibility of entering incorrect or already completed (Done) Jira issues. Most of the time developers enter the correct IDs but when they enter an already completed Jira Issue ID that creates a headache for the release team. We are looking for validating the status of the Jira Issue IDs and link the correct IDs only to the commit and ignore the incorrect IDs. So, we are looking for a programmatic (curl etc.) way to establish the Jira and Bitbucket integration using any of the server-side hooks.


Answers:
author: Julius Davies _bit-booster_com_
body: Our "[Control Freak](https://marketplace.atlassian.com/apps/1217635/control-freak-commit-checkers-and-jira-hooks-for-bitbucket?hosting=datacenter&tab=overview)" app does exactly this (rejects commits that refer to invalid Jira ids).

<https://marketplace.atlassian.com/apps/1217635/control-freak-commit-checkers-and-jira-hooks-for-bitbucket?hosting=datacenter>

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


Tags: bitbucket-data-center

data-center
How do I make a repository into a website
Asked by Ramaswami Family:

I want to figure out how to get a domain with .bitbucket.io at the end


Answers:
author: Ben
body: Hi [@Ramaswami Family](/t5/user/viewprofilepage/user-id/5430977)

Welcome to the Bitbucket Cloud community! :)

Please refer to our documentation concerning this, it provides instructions on how to publish a website with the .bitbucket.io domain:

* <https://support.atlassian.com/bitbucket-cloud/docs/publishing-a-website-on-bitbucket-cloud/>

Cheers!

- Ben (Bitbucket Cloud Support)


Tags: bitbucket-cloud

cloud
Public issue tracker, but issues are not visible?
Asked by robmoss:

I have a public issue tracker here:

[https://bitbucket.org/robmoss/particle-filter-for-python/issues?status=new\&status=open](https://bitbucket.org/robmoss/particle-filter-for-python/issues?status=new&status=open)

When I'm logged in, I can see there's one open issue. But when I view the issue tracker without being logged in, it says:

"No issues found. Try another search."

I have double-checked that the issue tracker is public, so I don't understand why issues aren't visible when I'm not logged in. Does anyone know what might be going on, or how to resolve this?


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

If an issue is created by a user that that is not a member of the repo's workspace, its status is going to be SUBMITTED and it will not be publicly visible. You will need to change its status to to OPEN so that it is visible to to everyone.

Bitbucket Cloud issue trackers were targeted by spammers last year, and many users' public issue trackers had a large number of spam issues. This is one of the measures we took after last year's incident.

Kind regards,  
Theodora

comments: author: robmoss
body: Hi Theodora,

Thank you very much, I had no idea that submitted issues aren't publicly visible! I've changed its status to open and it's now public.

All the best,Rob


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


author: Julius Davies _bit-booster_com_
body: Can you provide a screenshot of the \<Repository\> --\> Settings --\> Issue Tracker screen ?


Tags: bitbucket-cloud

cloud

issue-view
I don't see invitations by other accounts and i don't receive emails from Bitbucket either
Asked by ROXCODE:

Hello there!

Where do i see invitations sent by other accounts? I don't receive emails either so at the moment it's impossible to accept invitations. V frustrating. I've used Bitbucket for years and never had this issue before.

Kind Regards,

Rosario


Answers:
author: Syahrul
body: G'day, [@ROXCODE](/t5/user/viewprofilepage/user-id/5430941)

Welcome to the community!

From my observation, I haven't identified any problems with the invitation email being dispatched to your mailbox. The email may have been redirected to another folder within your mailbox.

I suggest checking your spam, 'Other' folders, or any other filters you may have in place, as the invitation email may be inadvertently redirected there.

Regards,  
Syahrul


author: ROXCODE
body: OMG you are absolutely right! I found i had a complex rule in place which was moving bitbucket emails to a folder in different mail box account! It would have been impossible to figure out without your hint. Thank you.


Tags: bitbucket-cloud

cloud
REST API using proxy returns 403
Asked by Dani Asztalos:

I'm creating a custom pipe, where I create a Report using the [rest API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-reports/#api-repositories-workspace-repo-slug-commit-commit-reports-reportid-put) and the proxies mentioned at the bottom of the [Code Insights page](https://support.atlassian.com/bitbucket-cloud/docs/code-insights/).

* Using the API as-is, with an Access Token in Auth header works.
* Running it in pipelines directly through python (not in docker), with <http://localhost:29418> proxy works.
* But running it from the packaged pipe in another repository, and using the <http://host.docker.internal:29418> proxy returns 403 with the following json.

```
{
    "arguments": {},
    "key": "report-service.general.forbidden",
    "message": "Not authorized"
}
```

What am I doing wrong?


Answers:
author: Dani Asztalos
body: It turned out I was passing an ACCESS TOKEN through headers and using the proxy, which resulted in 403. Removing the ACCESS TOKEN and using the proxy only resolved the issue.


author: Syahrul
body: G'day, [@Dani Asztalos](/t5/user/viewprofilepage/user-id/5408546)

Welcome to the community!

Could you try to add this to your pipe script and see if that helps?

```
export HTTP_PROXY=http://host.docker.internal:29418
export http_proxy=http://host.docker.internal:29418
export HTTPS_PROXY=http://host.docker.internal:29418
export https_proxy=http://host.docker.internal:29418
git config "http.${BITBUCKET_GIT_HTTP_ORIGIN}.proxy" http://host.docker.internal:29418
```

I believe you need to configure the git config proxy as well if it's from docker.

Regards,  
Syahrul

comments: author: Dani Asztalos
body: I am using the Rest api, not git, so setting the git proxy would not help.


Tags: bitbucket-cloud

bitbucket-pipelines

cloud

report

rest-api
Differences between Bitbucket cloud and on-prem & integration with Jira Cloud
Asked by Tomislav Tobijas:

Hi,

As I'm not a power user or administrator of Bitbucket, I would need some assistance here. We've received a question regarding Bitbucket on-prem vs. cloud version. Basically, we're migrating one Jira server instance to the cloud and the question is regarding Bitbucket - should we stay on on-prem version (I managed to find information that integration between Bitbucket server and Jira cloud is possible), or should we migrate Bitbucket to cloud too.

General questions are:

1. What are general/key differences between Bitbucket cloud and on-prem?
2. Are there any 'negative' outcomes if stay on Bitbucket on-prem or with moving it to cloud keeping in mind that Jira is moving to Cloud?

Cheers,  
Tom


Answers:
author: Theodora Boudale
body: Hi Tom,

Support for Server products ended on Feb. 15, 2024. If you have a Bitbucket Server license, you will no longer have access to tech support, security updates, and bug fixes. If you have a Data Center license instead, the latter does not apply and you will continue to have access to tech support, security updates, and bug fixes.

The two products (Bitbucket Cloud and Bitbucket Server/Data Center) have a different source code base. Many core features are the same, but there are also some differences. For example, server-side hooks or iterative reviews in pull requests are not available in Bitbucket Cloud yet. We are working on bridging the parity between Server/Data Center and Cloud. Bitbucket Cloud has a built-in CI/CD tool (Pipelines), and the ability to add a wiki or an issue tracker in a repo, which are not available on the Server.

Bitbucket Cloud also has a 4 GB limit on each repo, but if you get the Premium plan, we may be able to extend this up to 10 GB for certain repos.

You can read the following documentation with things to check before migrating:

* <https://support.atlassian.com/migration/docs/plan-your-bitbucket-server-to-cloud-migration/>

We also have the following documentation on the differences between administering Bitbucket Data Center and Cloud:

* <https://support.atlassian.com/migration/docs/differences-administering-bitbucket-data-center-and-cloud/>

Kind regards,  
Theodora


Tags: bitbucket-cloud

bitbucket-server

cloud-migration
Pipeline deployment for copying files between windows servers (self-hosted)
Asked by Jeremy Chin Wang Cheung:

Hi all,

I am doing PoC on the pipeline under windows env (self.hosted at the moment).

Understanding we can use atlassian/scp-deploy for scp'ing the files to other servers, however, my current PoC env is running Windows and don't have scp.

It there some ways to just copying files without the need for scp?

Thank you very much.


Answers:
author: Theodora Boudale
body: Hi Jeremy,

Pipes cannot be used with self-hosted Windows runners, as these runners do not use Docker containers.

Windows Runners use PowerShell to run pipeline steps on your Windows machine (host device), so the commands in your yml file's script are PowerShell commands. So, what you need is a way to copy files using PowerShell.

You can check some of the suggestions in the following StackOverflow post:

* <https://stackoverflow.com/questions/10741609/copy-file-remotely-with-powershell>

You can try it first on PowerShell (without a runner), and if you have a command that works then you can use it in your yml file with the runner.

Kind regards,  
Theodora

comments: author: Jeremy Chin Wang Cheung
body: thank you very much.


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


author: Igor Stoyanov
body: Hi [@Jeremy Chin Wang Cheung](/t5/user/viewprofilepage/user-id/5403988) . You could check these pipes:

* [rsync-deploy](https://bitbucket.org/atlassian/rsync-deploy/src/master/)
* [ftp-deploy](https://bitbucket.org/atlassian/ftp-deploy/src/master/)
* [sftp-deploy](https://bitbucket.org/atlassian/sftp-deploy/src/master/)
* or even [ssh-run](https://bitbucket.org/atlassian/ssh-run/src/master/) with your custom script

More pipes you could discover [at the Marketplace](https://bitbucket.org/product/features/pipelines/integrations)

Regards, Igor


Tags: bitbucket-pipelines

cloud

data-center

deployment

windows
"No Sonar data found for project "ABC_project". Please wait for the build to be finished or check yo
Asked by Shivika Sharma:

I am currently using Bitbucket v8.9.9 and installed the plugin for sonar for bitbucket. I also installed sonarqube version 9.9.3 community edition. The issue i am facing is whenever I raise a pull request to merge a feature branch with main branch i get below error:

<br />

**"No Sonar data found for project "ABC_project". Please wait for the build to be finished or check your build configuration and reload this page afterward".**

For every PR i am getting the same error.

Can anyone please suggest on this.


Answers:
author: Christian Ott _Mibex Software_
body: Hi

The error message suggests that no analysis of the pull request exists in the SonarQube project. You can check your configuration by following our [troubleshooting guide](https://mibexsoftware.atlassian.net/wiki/spaces/MSS/pages/2215346177/Troubleshooting).

Feel free to create a [support ticket](https://mibexsoftware.atlassian.net/servicedesk/customer/portal/1) if you cannot get it to work.

Kind regards,  
Christian - Mibex Software


Tags: bitbucket-server

server

sonarqube
Bitbucket webhooks with custom payload?
Asked by Charlie Misonne:

I need to execute a http request when a pull request in created in Bitbucket DC. The request will be received by an external application.

This can be done with the webhooks feature but I do not see any way to define a custom json payload. Bitbucket will always send it's own predefined JSON. Is that correct?

If that's really the case the only way to use the webhooks is when your target application expects that exact format?


Answers:
author: Aron Gombas _Midori_
body: I don't think you can customize the payload.

Instead you could try one of these:

1. Implement a little "proxy" in between Bitbucket and target system. This proxy would receive the built-in webhook's payload, and transform it to the "dialect" expected by the target system. There are many ways to build something like this, but it can only be done if the built-in payload carries every piece of information that the target system expects.
2. I think you can have automation rules triggered by the "pull request created" event. If so, then you can use *Send web request* automation action to send a request to the target system. This action allows customizing the request body, so it could work with your target system, too.


Tags: bitbucket-data-center

data-center