youngmon/atlassian-qna huggingface dataset:
Destination branch not filtering
Asked by Patrick Tangney:

Hi guys,

Having issues creating a PR - the destination branch is not filtering at all, the 'type to filter is also greyed out...

This was working as normal earlier

Anyone else experiencing the same ?

This is also happening using the create branch using the cloud create branch button.


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

I would like to ask some questions so I can better help you:

**1.** Could you please explain what you mean by 'destination branch is not filtering'? Are you unable to type a branch name in this field in order to filter branches? Or do you mean something different?

**2.** Do other team members of yours face the same issue when trying to create a PR on this repo?

**3.** Does this issue occur with one specific repo or with other repos as well?

**4.** What browser are you using and what version of this browser?

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud
Webhook Type
Asked by xicond:

I have webhook for pipeline notification to slack when it's success  
but it seems only for automated action  
If it's manual trigger, how to get the notification

because when someone trigger the manual, I might want to take precaution  
Or I might dont wanna wait or keep screen open for the manual step to be finished, just let it notify my computer


Answers:
author: Patrik S
body: Hello [@xicond](/t5/user/viewprofilepage/user-id/16360) , and thank you for reaching out to the community!

I tested on my end manually triggering a pipeline by both using the "Rerun" button, or defining a [custom manually triggered pipeline](https://support.atlassian.com/bitbucket-cloud/docs/pipeline-triggers/#Set-a-manual-pipeline), and for both of them, I received the notification that the pipeline succeeded in the Slack channel linked to my repository.

In this case, could you try opening the repository where the pipeline runs and navigate to **Repository Settings** \> **Slack Settings** and confirm if the event *pipeline succeeded* is configured in the *Repository-wide* section, or for the branch that pipeline is running?

![Screenshot 2023-09-07 at 12.20.48 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/279360i3DB95C04DB3BD0E9/image-size/large?v=v2&px=999 "Screenshot 2023-09-07 at 12.20.48 PM.png")

In the scenario where you are filtering the Slack notifications by the branch name, the branch/branch pattern should match the name of the branch pipeline that is running.

If you confirm the event is correctly configured in the Slack settings, but you are still not receiving the notification, we would kindly ask you to share the following

* A screenshot of your Slack settings page with the enabled notifications
* More details about how you are manually triggering the pipeline:
  * Is it a [branch triggered pipeline](https://support.atlassian.com/bitbucket-cloud/docs/pipeline-start-conditions/#Branches) or a [custom manually triggered pipeline](https://support.atlassian.com/bitbucket-cloud/docs/pipeline-start-conditions/#Custom--manual--pipelines) ?
  * By manually run, did you mean using the "Rerun" option, or the **Run Pipeline**button on the Pipelines page?

If you have any questions, feel free to ask.

Thank you, [@xicond](/t5/user/viewprofilepage/user-id/16360) !

Patrik S

comments: author: xicond
body: it is in yml write as  
trigger: manual  

**Run Pipeline** also has 2 meanings, run custom pipeline or Run manual trigger step  
I need one is the Run manual trigger step


Tags: bitbucket-cloud

bitbucket-pipelines

cloud
Where can I find documentation for the lifecycle object received on a Atlassian Connect app install
Asked by FD:

Hi,

We are building a new Atlassian Connect app on Bitbucket. The lifecycle object we receive on install/uninstall event contains fields that are bit ambiguous in meaning. We were trying to find documentation but cannot find any.

The object looks like

````
```
{
"key": "",
"publicKey": "",
"clientKey": "",
"baseUrl": "https://bitbucket.org",
"productType": "bitbucket",
"eventType": "installed",
"sharedSecret": "",
"actor":
{
},
"baseApiUrl": "https://api.bitbucket.org",
"principal":
{
},
"user":
{
}
}
````

In particular, what is the difference between the principle and the user field? And is the actor field no longer present? I had the actor field in Aug, but now, it is missing from the request.

Sincerely

FD


Answers:
author: Patrik S
body: Hey [@FD](/t5/user/viewprofilepage/user-id/5304349) and welcome to the Community!

Since this is more of an app development question, as you are building an Atlassian Connect application, I would suggest reaching out to our community dedicated to developers:

* <https://community.developer.atlassian.com/>

as they will have more expertise on this topic to assist you further with your question.

Thank you, [@FD](/t5/user/viewprofilepage/user-id/5304349) !

Patrik S


Tags: bitbucket-cloud

cloud
AWS S3 Deploy Pipe Issues
Asked by Samuel Bloch:

When trying to use the S3 pipe, it doesn't work if there are spaces in the local path

```
- pipe: atlassian/aws-s3-deploy:1.1.0
variables:
AWS_ACCESS_KEY_ID: $AWS_KEY # Optional if already defined in the context.
AWS_SECRET_ACCESS_KEY: $AWS_SECRET # Optional if already defined in the context.
AWS_DEFAULT_REGION: "us-east-1"
S3_BUCKET: "foo-bucket/bazz/"
LOCAL_PATH: "$BITBUCKET_CLONE_DIR/foo bar/folder"
```

This will fail.


Answers:
author: Ben
body: Hi Samuel,

Are you able to use the latest version of the pipe and see if you experience the same behaviour (1.3.0)?

Also, try creating a repository variable with the entire path and pass this through using this variable in the pipe parameters - does this make any difference?

The last thing I would try is to escape the path using ' single quotes instead of " double quotes.

Cheers!

- Ben (Bitbucket Cloud Support)

comments: author: Igor Stoyanov
body: [@Samuel Bloch](/t5/user/viewprofilepage/user-id/4207738) hi. Also some [useful link about escaping.](https://stackoverflow.com/questions/19858176/how-do-i-escape-spaces-in-path-for-scp-copy-in-linux)  

Regards, Igor


Tags: aws

bitbucket-cloud

bitbucket-pipelines

cloud
Invitation not email not received
Asked by Annissa Pereira:

My professor send me invitation email twice but I didn't receive it. What could be the problem?


Answers:
author: Mark C
body: Hi [@Annissa Pereira](/t5/user/viewprofilepage/user-id/5310255),

Welcome to the Atlassian community.

I checked our internal logs but I didn't see any bounced or blocked against your email address.  
Would it be possible for you to ask your professor to reinvite you by clicking the "Resend invitation" button?

If you still haven't received the invitation email, kindly check your inbox's spam and junk folders to see if the invitation email was caught up there or if the email is being filtered.

You can also check this knowledge-based article for more information about [email notifications not working](https://confluence.atlassian.com/bbkb/email-notifications-not-working-1224343600.html).

Let me know how it goes.

Regards,  
Mark C


Tags: unknown-hosting-type
How to access secured repository variables in windows runner?
Asked by Chris:

Hi!

When accessing repository variables in my windows runner pipeline via

```
$env:SOME_VAR 
```

everthing works EXCEPT when the variable is set to be "**secured**"! In that case the ENV is not set/empty!

How to access secured variables? Am i missing something or is this a bug?


Answers:
author: Mark C
body: Hi [@Chris](/t5/user/viewprofilepage/user-id/4484770),

Thank you for reaching out to the community.

<br />

You can safely access secured variables by following the solutions mentioned in this knowledge-based article. - [How to safely export secured variables in bitbucket pipelines](https://confluence.atlassian.com/bbkb/how-to-safely-export-secured-variables-in-bitbucket-pipelines-1189479471.html)

Regards,  
Mark C

comments: author: Chris
body: I can access all types of variables in our Linux runner, but with a Windows runner only "unsecured" aka normal variables work!


author: Chris
body: sorry, my bad! got it working now by additionally en-/decoding the secured values with base64


Tags: bitbucket-cloud

bitbucket-pipelines

cloud

windows
/pipe.sh: line 28: REMOTE_PATH: SSH_REMOTE_PATH variable missing.
Asked by Siddhant Pandey:

getting this problem during deployment of my pipeline test project can some one let me know what i am doing wrong here. i have inserted ssh publich key into my server and bitbucket as well i have created it on my local machine. and also generated fingerprint for know host using ip of my server. it is not working.

![4.png](/t5/image/serverpage/image-id/279067i701FCD9E6CE4BA37/image-size/large?v=v2&px=999 "4.png")![3.png](/t5/image/serverpage/image-id/279068i7A024B2642C192BD/image-size/large?v=v2&px=999 "3.png")![2.png](/t5/image/serverpage/image-id/279069i02DE573710A32E0B/image-size/large?v=v2&px=999 "2.png")![1.png](/t5/image/serverpage/image-id/279070i676A28BFBEFB31B3/image-size/large?v=v2&px=999 "1.png")


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

The error you received indicates that this pipe requires you to provide a variable named **REMOTE_PATH**containing the path in the remote server where you want to deploy the files.

I see in your pipe definition that you have configured a variable named PATH containing the destination folder of the deployment, but the pipe actually expects this information in a variable named **REMOTE_PATH**.

Following is an example of the pipe definition containing all the required variables :

```
 - pipe: atlassian/rsync-deploy:0.9.0
    variables:
      USER: $DEPLOY_USER
      SERVER: $DEPLOY_SERVER
      REMOTE_PATH: '/var/www/build/'
      LOCAL_PATH: 'build'
```

You can try configuring the pipeline based on the example above and let us know how it goes.

Also, to check for the pipe's schema containing all the available variables (including required and optional ones), and examples of using that pipe, you can refer to its official documentation below:

* [atlassian/rsync-deploy \| Pipe](https://bitbucket.org/product/features/pipelines/integrations?search=rsync&p=atlassian/rsync-deploy?)

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

Thank you, [@Siddhant Pandey](/t5/user/viewprofilepage/user-id/5236498) !

Patrik S

comments: author: Siddhant Pandey
body: [@Patrik S](/t5/user/viewprofilepage/user-id/4603309) thanks man it is working properly thank alot for helping me men.


author: Patrik S
body: Hey [@Siddhant Pandey](/t5/user/viewprofilepage/user-id/5236498)

Happy to have been of some help :)

If you ever need assistance with Bibtucket, feel free to reach out here on Community!


Tags: bitbucket-cloud

bitbucket-pipelines

cloud
List pull requests that contain a commit not giving the full output reponse
Asked by Akshara Anilkumar:

When I am using this url it is not giving the full reponse as which is shown in the document of bitbucket cloud. Is there any reason why this is happening ?(document link: <https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/#api-repositories-workspace-repo-slug-commit-commit-pullrequests-get>)

curl --request GET \\ --url '<https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/commit/{commit}/pullrequests>' \\ --header 'Accept: application/json'

This is how I am getting my output but whereas in the document it is showing a lot more .

{  
"type": "paginated_pullrequests",  
"values": \[  
{  
"type": "pullrequest",  
"id": 15,  
"title": "userStory.java created online with Bitbucket",  
"links": {  
"self": {  
"href": "<https://api.bitbucket.org/2.0/repositories/ck-mux-bitbucket-connector/bitbucket_repo/pullrequests/15>"  
},  
"html": {  
"href": "<https://bitbucket.org/ck-mux-bitbucket-connector/bitbucket_repo/pull-requests/15>"  
}  
}  
}  
\],  
"page": 1,  
"pagelen": 50  
}


Answers:
author: Syahrul
body: Hey [@Akshara Anilkumar](/t5/user/viewprofilepage/user-id/5304231)

Welcome to the community!

I can reproduce the same response as you, so I am checking this internally to see if the endpoint has a bug.

As a workaround, I believe if you use the \`?fields=\` options to get the fields you need, it should return the desired outcome, so please try it and let me know if that works.

Regards,  
Syahrul

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

Thankyou for the reply. Actually its working when the endpoint is given like this: <https://api.bitbucket.org/2.0/repositories/ck-mux-bitbucket-connector/bitbucket_repo/commit/6114c34588678f9c4b30580c85c558e5801ae0c2/pullrequests?fields=%2Bvalues.merge_commit>

Is it possible to resolve this bug as soon as possible?


Tags: bitbucket-cloud

cloud
Not receiving E-mail - Suppresion List check
Asked by Florin Hristache:

Hello,

I am the admin of two projects and for the past two days I am not receiving the notification E-mails anymore.

I have checked with Admin Notification Helper, I was previously receiving the notifications, I have checked personal settings and I have them enabled everywhere (+proper permissions. From what I have read around, it is something to do with the Atlassian Suppression list.

Could you check if my email is added to your suppression list?

Thank you in advance!

-Florin


Answers:
author: Ben
body: G'day Florin!

We have checked our email logs and have found that we are successfully sending emails to your mail server however the following error was received from your mail server for your email address:

```
554 5.7.1 [internal] recipient address was suppressed due to customer policy

```

**This error is encountered on your mail server when any of the following conditions are met:**

* The address was invalid (address does not exist)
* The user clicked the list-unsubscribe header
* The user clicked one of your emails and flagged it as SPAM.
* This FBL (FeedBack Loop) event should add that email address to your Suppression List.

**I would suggest reaching out to your email administrator** to whitelist our email accounts as follows, then try to re-send the invitation once this has been performed:

* noreply@am.atlassian.com
* no-reply@atlassian.com
* noreply@mailer.atlassian.com
* notifications-noreply@bitbucket.org  

Cheers!

- Ben (Bitbucket Cloud Support)


Tags: atlassian-support

bitbucket-cloud

cloud

email

notification
The overall deployment failed because too many individual instances failed deployment, too few healt
Asked by Suraj Prakash:

Hi Friends! I am implementing pipeline . My application is hosted on aws EC2 instance. The Application is build in C# .Net .

* I have created the Pipeline in Bitbucket in my Repository.
* Also Created the appsec.yml in it.
* Declared variable in Pipeline.Yml
* Created the Code deploy configuration in aws.
* Also installed code deploy agent on ec2 instance.

I am getting the following below error. Please help.

![aws edited.png](https://community.atlassian.com/t5/image/serverpage/image-id/278979i7472B05A489C9A10/image-size/large?v=v2&px=999 "aws edited.png")![Bitbucket error.png](/t5/image/serverpage/image-id/278978i469598DFD36FF1B9/image-size/large?v=v2&px=999 "Bitbucket error.png")


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

Are you using the pipe **atlassian/aws-code-deploy** in your bitbucket-pipelines.yml  
file in order to deploy?

If so, I would suggest adding the following variable in the pipe's definition in your bitbucket-pipelines.yml file (reference: <https://bitbucket.org/atlassian/aws-code-deploy/src/master/>):

```
DEBUG: 'true'
```

and observe the output of the pipe. This is to confirm if the pipe is indeed failing with the error
> The overall deployment failed because too many individual instances failed deployment, too few healthy instances are available for deployment, or some instances in your deployment group are experiencing problems.

If this is the case, please check the following documentation from AWS (search for this specific message on this page):

* <https://docs.aws.amazon.com/codedeploy/latest/userguide/error-codes.html>

There are resources there that may help you resolve the issue.

If you still cannot figure it out, I would suggest reaching out to AWS support team, as the issue seems to be related to your AWS EC2 instance rather than Bitbucket.

If the output of pipe shows a different error when you add **DEBUG: 'true'**, please feel free to post it here and we will look into it.

Kind regards,  
Theodora

comments: author: Suraj Prakash
body: Hi Theodora,

Thank you so much for quick reponse. Let me check!!

Thanks \& Regards,

Suraj Prakash


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

Regards,  
Theodora


Tags: bitbucket-cloud

cloud
Please fix google-gke-kubectl-run, backup folder means an oversized image
Asked by Tommo:

* the version of the pipe -

  ```
  atlassian/google-gke-kubectl-run:3.0.0
  ```

* relevant logs and error messages

  ```
  google-gke-kubectl-run:3.0.0-without-backup-folder <none> 61abf4e9da2d 20 seconds ago 2.08GB

  google-gke-kubectl-run:3.0.0 <none> f637d02b9abb 7 minutes ago 2.81GB
  ```

* steps to reproduce  
  Modify the various docker images and compare.

<br />

After consulting Google's version of the docker file <https://github.com/GoogleCloudPlatform/cloud-sdk-docker/blob/master/debian_component_based/Dockerfile>  

And comparing that with Atlassian's version: <https://bitbucket.org/atlassian/google-gke-kubectl-run/src/master/Dockerfile> I conclude that the Atlassian pipe google-gke-kubectl-run lacks this step.  
\`rm -rf /google-cloud-sdk/.install/.backup\`  
As a result, the image is over 200MB larger as a result, over 25% larger than it needs to be. Since the image is over 700MB now, you should definitely remove the backup from your image.  

More specifically, modify line 27:

```
- RUN ./google-cloud-sdk/install.sh --quiet
```

```
+ RUN ./google-cloud-sdk/install.sh --quiet && rm -rf /google-cloud-sdk/.install/.backup
```

<br />

<br />

Atlassian's "slim" version based on 442.0.0:  
753.52 MB <https://hub.docker.com/r/bitbucketpipelines/google-gke-kubectl-run/tags>  

Google's slim version:  
424.6 MB [https://hub.docker.com/r/google/cloud-sdk/tags?page=1\&name=442.0.0-slim](https://hub.docker.com/r/google/cloud-sdk/tags?page=1&name=442.0.0-slim)  

Note that this is compressed size. The majority of that is the \`/google-cloud-sdk/.install/.backup\` folder but it looks like you might get 100MB smaller.   

Uncompressed I see 2.81GB vs 2.08GB just by removing the \`/google-cloud-sdk/.install/.backup\` directory.  
Build just like it's set up in the Bitbucket:  

```
> docker build -t docker build -t google-gke-kubectl-run:3.0.0 .
```

Modify line 27 as described and build:

```
> docker build -t google-gke-kubectl-run:3.0.0-without-backup-folder .
```

```
> docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
google-gke-kubectl-run 3.0.0-without-backup-folder 61abf4e9da2d 20 seconds ago 2.08GB
google-gke-kubectl-run 3.0.0 f637d02b9abb 7 minutes ago 2.81GB
```


Answers:
author: Igor Stoyanov
body: [@Tommo](/t5/user/viewprofilepage/user-id/4233489) hi. New [pipe version](https://bitbucket.org/atlassian/google-gke-kubectl-run/src/3.1.0/) released with fixes you suggested.

Regards, Igor

comments: author: Tommo
body: Looks good to me. Saved 193MB.  


author: Igor Stoyanov
body: [@Tommo](/t5/user/viewprofilepage/user-id/4233489) hi. Thanks for your investigation. We will fix this in a future releases and notify you.  

Regards, Igor


Tags: bitbucket-cloud

bitbucket-pipelines

cloud

google

kubernetes
Cucible maximum data size
Asked by FEAT Erwann:

Dear all,  

We've a licence for a crucible server (2.3.6).  

This server is very slow and its data size is:  

-around 4Go of mysql database data  

-110Go of file data ( under FISHEYE_INST)  

Is there a limit of data size for this server ? What are your recommandations about this ?  

What's more I've tried to upgrate it to version 2.7.8 unsucessfully.  

After more than 10h of migration I've stopped the server to rollback all to the 2.3.6 version.  

<br />

Thanks for your help.


Answers:
author: JamieA
body: Fisheye/Crucible is never going to be fast unless you only have a toy repo indexed. But for comparison we have 500Gb of index data... performance is OK after it received a lot of admin love recently, which mainly comprised identifying all the bad "svn copies" (of branches and tags) and automatically adding exclusion rules for them. We then blew away the globalfe cache and had it recreate that.

Performance is now no better than OK at best, but it's a big improvement. So to answer your question, no, no upper limit AFAIK.
Using Fisheye in Jira on demand
Asked by Finn Harsfort:

Hi Atlassian

We are the happy users of your brilliant JIRA on demand product. We are currently running a Fisheye evaluation on our JIRA ondemand.

We wanted to use Mecurial, but it seems that Fisheye is already configured for SVN.

How do we change this, or is Mucurial not supported in the ondemand version?

If not, when is it expected to be supported?

Can we start using SVN now and later migrate repository to Mecurial?


Answers:
author: JohnA
body: Hi there,

Mercurial isn't currently supported by FishEye OnDemand because the bundled version is v2.5.7, whereas Mercurial is only supported from FishEye v2.7 onwards. I know that our developers are working hard to get the latest version of FishEye bundled for the OnDemand platform but due to the differences in architecture it takes a while to port the applications over and a while longer to implement all the customisations for the application to be truly available "OnDemand".

I'm not aware of a date when FishEye v2.7 will be bundled on the OnDemand platform but I do know that our developers only ever release products when they're ready, rather than to deadlines that have been set and must be met whether the product is ready or not. Therefore, the best answer I can give you at the moment regarding Mercurial support for FishEye OnDemand is that it will be available soon. However, you can start using SVN and then later migrate the repository to Mercurial. There are a number of tools available to assist you with the conversion, but I would suggest doing some research before committing to it as a solution.

All the best,

John


author: ShridharS
body: Hi  

Can anybody please tell me the procedure of "How to configure the SVN subversion with Fisheye for source repository" in JIRA atlassain Ondemand?

This is on high priority and it will be highly appreciated on providing the information.

**Thanks \& Regards,**   
**Shridhar Samala**


author: Rob
body: I assume this is still the case? I'm currently evaluate Jira / Fisheye and other plugins. But also can't seem to configure fisheye for GIT in bitbucket

Thanks

Rob


Tags: cloud