youngmon/atlassian-qna huggingface dataset:
User can't see/access apps from drop down menu
Asked by Patrick Till:

Hi

We have a few apps that all our users make daily use of.

I received a report, and confirmed, that one user no longer sees any Apps on the drop down menu.

All other users still have access to this list.

Please assist.

![2024-03-20 09_20_00-Medical Information Technology, Inc. Mail.jpg](/t5/image/serverpage/image-id/313201i6E2617A7240D073D/image-size/large?v=v2&px=999 "2024-03-20 09_20_00-Medical Information Technology, Inc. Mail.jpg")![2024-03-20 09_15_36-Patrick's Dashboard - Jira Service Management.jpg](/t5/image/serverpage/image-id/313200iAC7615654B3691CE/image-size/large?v=v2&px=999 "2024-03-20 09_15_36-Patrick's Dashboard - Jira Service Management.jpg")


Answers:
author: Sebastian Krzewi?ski
body: Hi [@Patrick Till](/t5/user/viewprofilepage/user-id/1971556)

Please check if user still have same permissions or is assigned to the same groups or check apps permissions. Some of apps like BigPicture or Tempo have own set of permissions that allows users see apps.

Regards,

Seba

comments: author: Patrick Till
body: Thank you.

I identified the issue with the user's browser's colour scheme.  
They had white on white.


Tags: app

cloud

jira-service-management

jira-service-management-cloud
Can we manage the whitelist via any sort of API calls?
Asked by Tom Southwood:

WE have users with dynamic IP addresses and have systems that manage them, is it possible to manage what IP addresses are in the whitelist via an API call rather than having to use the web based UI?


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

I'm afraid that it is not possible to manage a workspace's allow-listed IPs via API in Bitbucket Cloud. This is only possible via the UI at the moment.

We have a feature request for providing an API endpoint to do that:

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

The request has been closed as it is not likely to be worked on in the near future. However, I would recommend adding a comment there to express your interest, as our product managers continue to monitor even closed requests.

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

Kind regards,  
Theodora


author: Oday Rafeh
body: Yes, it is possible to manage the whitelist in Bitbucket via API calls. The Bitbucket API provides endpoints for managing IP whitelists.

You can use the Bitbucket REST API to retrieve and update the list of IP addresses in the whitelist for a repository or for the entire Bitbucket instance.

Here are the steps to manage the whitelist via API calls:

Retrieve the current whitelist for a repository or the entire Bitbucket instance using the following API endpoint:

```
GET /rest/api/latest/application-properties/feature/repository.whitelist
```

This will return a JSON object containing the current whitelist.

Modify the whitelist as needed. You can add or remove IP addresses by updating the JSON object returned by the previous API call.

Update the whitelist using the following API endpoint:

```
PUT /rest/api/latest/application-properties/feature/repository.whitelist
```

Provide the modified JSON object in the request body.

You will need to authenticate your API calls with the appropriate credentials. You can use OAuth or personal access tokens for authentication.


Tags: bitbucket-cloud

cloud
Source maps not uploaded to Sentry
Asked by Lalit:

We use Expo-managed workflow for our apps. And we have been using pipelines to send OTA updates, which works really well.

We have s \`postPublish\` hook that uploads our source maps to sentry for better tracing the errors. But we are getting **\[10:11:14\] Error uploading sourcemaps to Sentry: Could not find the SHA of the previous release in the git history. If you limit the clone depth, try to increase it. Otherwise, it means that the commit we are looking for was amended or squashed and cannot be retrieved. Use --ignore-missing flag to skip it and create a new release with the default commits count.**error since the last few builds. We haven't changed anything in our pipeline so maybe something changed internally?

I asked about the issue in the Github repo [here](https://github.com/expo/sentry-expo/issues/326), but they refer to it as Sentry-specific or Bitbucket pipeline issue.


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

Just to give you some context, Pipelines builds run in Docker containers. For every step of your build, a Docker container starts using the image you have specified in your bitbucket-pipelines.yml file. The repo is cloned in that container, and then the commands of the step's script are executed. When the step finishes that Docker container gets destroyed.

Do the pipeline builds with this issue run on a branch definition? For Pipelines running on a branch, this specific branch is cloned with a default depth of 50 (the last 50 commits of this branch will get cloned).

Based on the error message you posted, it looks like a command in your build is trying to find an earlier commit that is not available in the clone. If your build needs all commits of this branch to be available, you can add the following in your bitbucket-pipelines.yml, either as a top-level configuration for all steps or to a single step (this way all the commits of the branch will get cloned):

```
clone:
  depth: full
```

Documentation for reference:

* <https://support.atlassian.com/bitbucket-cloud/docs/git-clone-behavior/>

Please feel free to let me know if this works for you and if you need anything further!  

Kind regards,  
Theodora


Tags: bitbucket-pipelines

cloud

sentry
bitbucket-pipelines, build using ACR
Asked by Bo Christensen:

Hi, I have tried to solve this problem but have failed.

I need to build a docker image using bitbucket-pipelines and ACR.

I need examples of how to write the bitbucket-pipelines.yml

using 'az acr build' and how to push the image into ACR.

Please advise.

/Bo Christensen


Answers:
author: Theodora Boudale
body: Hi Bo,

Just to give you some context, Pipelines builds run in Docker containers. For every step of your build, a Docker container starts using the image you have specified in your bitbucket-pipelines.yml file. The repo is cloned in that container, and then the commands of the step's script are executed. When the step finishes that Docker container gets destroyed.

If you want to execute commands like 'az acr build', the Azure CLI needs to be installed on the Docker image that is specified as a build container in your bitbucket-pipelines.yml file. Microsoft provides the Docker image **mcr.microsoft.com/azure-cli** that has Azure CLI pre-installed. You can use it by specifying it in your bitbucket-pipelines.yml file as follows:

```
image: mcr.microsoft.com/azure-cli
```

This is the documentation for the Docker image options in bitbucket-pipelines.yml

* <https://support.atlassian.com/bitbucket-cloud/docs/docker-image-options/>

If you use a different Docker image as a build container, you will need to install Azure CLI in the container by adding the necessary commands in the script of your step. So, it may be easier to use **mcr.microsoft.com/azure-cli** instead.

You should then be able to use commands from Azure CLI in the script of your step. For the exact commands that you need to use, you will need to check Azure CLI documentation:

* <https://learn.microsoft.com/en-us/cli/azure/reference-index?view=azure-cli-latest>

If you have any questions, please feel free to reach out.

Kind regards,  
Theodora


Tags: bitbucket-cloud
Storage
Asked by leonng:

Hi there,

I'm confusing about the storage. The plan said that a 1GB Git LFS. Is this 1GB include all of repository? Also, the limit of repository is 4GB. Is this 4GB mean all repository in a project or workplace?If No, what is storage limit of a user?

Best Regards,  
Leon


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

Every repository in Bitbucket Cloud has a limit of 4 GB. This limit concerns the size of the core .git repo and not the LFS content. We don't have any limit on the amount of space that all .git repos of a project or a workspace use.

If you track files with Git LFS in a Bitbucket Cloud repo, these files are stored outside the .git repo on a different server. The limit of 1 GB Git LFS with the Free plan applies to the workspace, and it is shared across all the repos that belong to the workspace.

For example, if repo-a uses 300 MB of Git LFS and repo-b (belonging to the same workspace as repo-a) uses 500 MB of Git LFS, then the total of 800 MB is counted against the 1 GB Git LFS.

If you have any questions, please feel free to reach out!

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud
Remove Spam on site
Asked by Party EntPop:

How do I get a spammy link removed from this website?

<https://bitbucket.org/Andrewpaul9005/blog/wiki/Charleston%20Male%20Strippers>


Answers:
author: Theodora Boudale
body: Hi [@Party EntPop](/t5/user/viewprofilepage/user-id/5172351),

Thank you for reporting this. We have taken action and this content should no longer be accessible.

Please feel free to reach out if you have any questions.

Kind regards,  
Theodora


author: Nic Brough -Adaptavist-
body: Welcome to the Atlassian Community!

Either ask the admins of the Bitbucket system to do something about it, or report it to abuse@atlassian.com


Tags: bitbucket-cloud
trigger pipeline based on tag on branch
Asked by dschneider:

Is there any way to trigger a pipeline based on a tag on a branch?

currently I'm using :

```
pipelines:
  default:
   - step: *build-package
   - step: *generate-docs

  tags:
    v*.*.*:
      - step: *build-package
      - step: *generate-docs 
      - step: *publish-docs
```

but I would like the default to only apply to dev branches (exclude master) and then master branch to only build when a tag is applied.


Answers:
author: dschneider
body: To answer my own question, a couple links online suggest that bitbucket does not let you exclude branches so I need to create a dummy branch trigger for master. I haven't had a chance to push anything to master so this is untested but I think it should only trigger a build on master when a tag is pushed. :fingers-crossed:

```
pipelines:
branches:
'**':
- step: *build-package
- step: *generate-docs
'master':
- step:
script:
- echo "nothing to do for master branch"
tags:
v*.*.*:
- step: *build-package
- step: *generate-docs
- step: *publish-docs
```


author: MiguelQueiroz
body: I need this too, because when pushing tags for the staging branch, it does into the pipeline as "production too".

I used Bitrise before, and pipeline on a tag on a specific branch was totally possible. And I need commits to master with tags to trigger the pipeline. But only for master. To staging branch the steps are different.


author: Riley Venable
body: Yes, you can trigger a pipeline based on a tag on a branch using the "Tags start condition" option in the bitbucket-pipelines.yml file.

comments: author: dschneider
body: can you provide anexample?

```
pipelines:
  branches:
    '**':
      - step: *build-package
      - step: *generate-docs
    'master':
       tags:
         v*.*.*:
           - step: *build-package
           - step: *generate-docs
           - step: *publish-docs
```

i tried something like this but I don't think you can nest tags under a branch. I really need to specify all branches **except** master for the first part and then have a separate tags section that applies to any branch


author: dschneider
body: Would this make sense to exclude master except when tags are pushed to master?

```
pipelines:
  branches:
    '[!master]**':
      - step: *build-package
      - step: *generate-docs

  tags:
    v*.*.*:
      - step: *build-package
      - step: *generate-docs
      - step: *publish-docs
```


author: MiguelQueiroz
body: An example would be nice, because I need to only trigger the pipeline when on master branch and with tags "\*.\*.\*"


Tags: bitbucket-cloud

cloud
Build minutes not resetting after purchasing plan
Asked by Shivam Bisht:

Hello,  
From the last couple of weeks I was testing the Bitbucket pipelines using the free plan. After my Bitbucket Pipelines free plan expired, my subsequent pipelines paused as expected. However, I have been added as a user to a workspace that has purchased a plan, but my build minutes quota has not been replenished. What could be the issue or what steps should we take to resolve this?


Answers:
author: Theodora Boudale
body: Hi [@Shivam Bisht](/t5/user/viewprofilepage/user-id/5172019),

A Bitbucket Cloud user can be e member of multiple workspaces. A billing plan and the Pipelines minutes that come with it are associated with a certain workspace, and they can be used only by the repositories that belong to that workspace.

For example, if you are a member of both

* Workspace-A on the Free plan
* Workspace-B on the Standard Plan

then the repositories that belong to Workspace-A cannot use the build minutes of Workspace-B. The build minutes that come with the Standard plan of Workspace-B can be used only by the repositories belonging to Workspace-B.

I hope this helps. If you have any further questions, please feel free to reach out.

Kind regards,  
Theodora


author: Riley Venable
body: It is possible that the workspace's purchased plan does not include additional build minutes for individual users. It is recommended to check the details of the purchased plan or contact Bitbucket support for further assistance.


Tags: bitbucket-cloud

bitbucket-pipelines

cloud
Script runner unable to resolve class for com.atlassian.bitbucket.scm
Asked by Pavan Kumar Nayakanti:

Am trying to use below libraries to introduce a merge check  
import com.atlassian.bitbucket.permission.Permission  
import com.atlassian.bitbucket.permission.PermissionService  
import com.atlassian.bitbucket.repository.RepositoryService  
import com.atlassian.bitbucket.scm.pull.MergeRequest  
import com.atlassian.bitbucket.scm.pull.MergeRequestCheck  
import com.atlassian.bitbucket.scm.pull.MergeRequestCheckContext  
import com.atlassian.bitbucket.scm.pull.MergeRequestCheckResult  
import com.atlassian.bitbucket.user.SecurityService

But the script could not be compiled, due to inability of resolving below classes. What i might be missing here? Please advise.

```
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:Script100.groovy: 5: unable to resolve class com.atlassian.bitbucket.scm.pull.MergeRequestCheck @ line 5, column 1.   import com.atlassian.bitbucket.scm.pull.MergeRequestCheck   ^Script100.groovy: 6: unable to resolve class com.atlassian.bitbucket.scm.pull.MergeRequestCheckContext @ line 6, column 1.   import com.atlassian.bitbucket.scm.pull.MergeRequestCheckContext   ^Script100.groovy: 7: unable to resolve class com.atlassian.bitbucket.scm.pull.MergeRequestCheckResult @ line 7, column 1.   import com.atlassian.bitbucket.scm.pull.MergeRequestCheckResult   ^3 errors
```

.


Answers:
author: Dmitry Trubin
body: <https://docs.atlassian.com/bitbucket-server/javadoc/5.7.0/spi/reference/com/atlassian/bitbucket/scm/pull/MergeRequestCheck.html>

> **This interface is deprecated.**   
> in 5.0 for removal in 6.0.

You are likely using Bitbucket of version higher than 6.0.

----

Refer to the documentation for the respective classes to find a replacement.


author: Yannis Argyropoulos __ScriptRunner - The Adaptavist Group__
body: Hi [@Pavan Kumar Nayakanti](/t5/user/viewprofilepage/user-id/5171959)

As [@Dmitry Trubin](/t5/user/viewprofilepage/user-id/4737249) already said, some of these classes are deprecated and you will not be able to use them with bitbucket 6 or higher. Currently, ScriprRunner for bitbucket supports Bitbucket server 7.5.0 or higher.  
Scriptrunner's merge checks will give you access to a 'mergeRequest' object, which you can use to access any merge-request-related information you need to apply your merge check logic.  
I can help you further, if you let me know what kind of merge check you want to do.


Tags: bitbucket-server

merge

scriptrunner

server
UtiPath software not available
Asked by Jennifer.F.Weaver:

My UtiPath software CCB's are not listed in Software Center. It has been more than two days since my request.


Answers:
author: Nic Brough -Adaptavist-
body: Welcome to the Atlassian Community!

I think you are in the wrong place. I don't recognise any of that as being Atlassian related.

If it is, then could you explain how?

I suspect you may need to ask your admins, not an Atlassian community!


Tags: bitbucket-server

server
How to send Bitbucket logs to SIEM or Syslog Server?
Asked by Dharam Desai:

Is there a way to send Bitbucket logs to a Syslog Server.


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

If you have an Atlassian Access subscription, Bitbucket Cloud event logs can be tracked in Atlassian Access. The audit log feature in Atlassian Access includes an API endpoint that can be used to retrieve logs and export them to a SIEM tool.

You can read more about this in the following blog post we published in November:

* <https://bitbucket.org/blog/bitbucket-audit-logs-are-now-available-in-atlassian-access>

If you have any questions, please feel free to reach out.

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud
Can't do sync or pull from a remote bitbucket branch
Asked by Oshan Silva:

I'm using VS 2022 and when I try to do a sync or pull operation using visual studio it prompts for the bitbucket password. When I enter the password (which is the same as login password for the bitbucket account) there is an error message saying "the pull operation failed". Please see the attached error log.

P.S. I haven't had any issues until this morning.

Thanks

Oshan

![bitbucket 1.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/245845i64D5CD621A35B53B/image-size/large?v=v2&px=999 "bitbucket 1.PNG")

![bitbucket 2.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/245844iD45EC06A28E297C4/image-size/large?v=v2&px=999 "bitbucket 2.PNG")


Answers:
author: Patrik S
body: Hello [@Oshan Silva](/t5/user/viewprofilepage/user-id/5171356) ,

Welcome to Atlassian Community!

Last year [Bitbucket Cloud deprecated the usage of account passwords for git activity and API calls](https://community.atlassian.com/t5/Bitbucket-articles/Announcement-Bitbucket-Cloud-account-password-usage-for-Git-over/ba-p/1948231#:~:text=Beginning%20March%201%2C%202022%2C%20you,the%20Bitbucket%20Cloud%20REST%20API.). The account password is the one used to login into the Bitbucket website.

Now, when using git over HTTPS you should create and use an [App Password](https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/) as the credential for authentication, instead of the account password.

In this case, could you try [creating an app password](https://support.atlassian.com/bitbucket-cloud/docs/create-an-app-password/) in your bitbucket account, and using this app password when prompted by git to provide your credentials?

Let us know how it goes and if using the app password fixes the issue.

Thank you, [@Oshan Silva](/t5/user/viewprofilepage/user-id/5171356) !

Patrik S

comments: author: Oshan Silva
body: Thanks, [@Patrik S](/t5/user/viewprofilepage/user-id/4603309) for the quick reply. I was trying to authenticate the pull/sync operations using both the app password and the account password. Both passwords got refused continuously.   
Half an hour later it got resolved automatically, and I could perform a pull operation.


Tags: bitbucket-cloud

cloud
aws-s3-deploy fails - Feels like not deleting all S3 files before upload.
Asked by Jason Redwood:

This is an intermittant issue, but it does look like it occurs more often when redeploying (uploading from bitbucket pipeline to S3) an older build over the top of a newer build.

It looks like the files are not fully or properly being deleted in the S3 bucket before the upload occurs and I often find the files in the s3 bucket are not accurate with the build

The aws-s3-deploy:1.1.0 config I am using is

\`\`\`  
- pipe: atlassian/aws-s3-deploy:1.1.0  
variables:  
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID  
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY  
AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION  
S3_BUCKET: $AWS_PROD_S3_BUCKET  
LOCAL_PATH: "output"  
DELETE_FLAG: "true"

\`\`\`

As mention, the issues dont seem to occur when incrementally deploying later builds, or at least much much less often, the issue seems to occur when deploying a later build, then redeploying an earlier build later on.

When the issue occurs, to resolve it, I login to AWS and manually delete all the files, then do the deployment and everything works as expected.

Is anyone else experiencing this issue or does someone know what I might be doing wrong?


Answers:
author: Igor Stoyanov
body: [@Jason Redwood](/t5/user/viewprofilepage/user-id/5171307) hi . Thanks for your question. This pipe based on [aws s3 sync](https://docs.aws.amazon.com/cli/latest/reference/s3/sync.html) where DELETE_FLAG is option:  
\`--delete (boolean) Files that exist in the destination but not in the source are deleted during sync\`.   
To test your case you could try directly call \`aws s3 sync\` command inside pipelines script, and investigate the behaviour.  

Regards, Igor


Tags: aws

bitbucket-cloud

bitbucket-pipelines

cloud
Cache not found - single step Pipeline build
Asked by sid6mathur:

Hi folks,

My pipeline build is unable to persist the $HOME/.cache directory across builds, hence running very slowly. Can someone find any errors in the caching setup below?

Log message in the "Build setup" phase:

> Cache "mytool-cache-dir: $HOME/.cache": Downloading  
Cache "mytool-cache-dir: $HOME/.cache": Not found  
My Pipeline YAML simply downloads a CLI tool off the web, and runs it for a while. The network downloads fetched by the tool live in **$CWD/.cache** of the tool run, and should be persisted across repeat runs of the build.  

```
image: atlassian/default-image:4

pipelines:

default:

 - step:

name: 'geofeed-finder wtf'

size: 2x

caches:

 - `mytool`-cache-dir

script:

 - $HOME/bin/`mytool`-linux-x64 -v

 - echo "Starting `mytool`"

 - $HOME/bin/`mytool`-linux-x64 -c 1 -g 1 --keep-non-iso --keep-invalid-subdivisions --download-timeout 10 -o $HOME/latest.csv

 - echo "Finished `mytool`"

 - wc -l $HOME/latest.csv

artifacts: # defining the artifacts to be passed to each future step.

 - $HOME/latest.csv

definitions:

caches:

`mytool`-cache-dir: $HOME/.cache 
```


Answers:
author: sid6mathur
body: I realized after posting this that the $PWD is not $HOME, which is my assumption in the above script. So I remove $HOME relative paths and let them be either relative to $(pwd) (present working directory) or better still the $BITBUCKET_CLONE_DIR variable.

So now both the cache works and the artefacts are found correctly after the build is done. Yay!


Tags: bitbucket-cloud

cloud