Aneita Atlassian Team

Hi Marcus, Thanks for reaching out and apologies for the delay in replying. Just to clarify, are you using Bitbucket Pipelines or Jenkins for your builds? The API is for getting the status of Bitbucket Pipelines builds, not Jenkins builds. Aneita

Hey Alex, Thanks for reaching out and so sorry for the delayed response! Was this something that you were able to resolve? If not, can you please raise a support ticket so that we can look at your repository and configuration in more detail? Thanks, Aneita

Hey Nate, Thanks for reaching out! What are you interested in this information for? Is there something you're trying to achieve? We currently don't have exactly what you're asking for, but you might be able to achieve something similar with the deployment preview? If your deployment step is configured as a manual step,…

Hey David, Thanks for reaching out! We currently don't support project-level / multi-repo dashboards for pipeline or deployment activity, but we have a few open feature requests to support this that you might want to vote for / follow:…

Hey @Joan Vilariño In the absence of a plugin that does this, one way to wait for the result of the quality gate is to poll their system within your pipeline. For example, you can add a loop to your pipeline after the scan is triggered, which will check whether the scan has completed (or until some timeout is reached).…

Hey @rajeshkanhasoft Thanks for reaching out. Email notifications are currently only sent for failed Pipelines builds. If your team uses Slack, we recommend that you use the Bitbucket Slack integration as it allows you to configure a much wider range of notifications for Pipelines and Deployments. If this isn't an option…

Hey @daumie Thanks for reaching out. Can you give me a little bit more context on what you're trying to do? Do you want to have access to another repository's code instead of the code that's in the repository that is running the pipeline or on top of the code in the repository that is running the pipeline? Can you also…

Hey @Sebastiaan Van Hoecke Have you added the `bitbucket-pipelines.yml` file to your repository? Pipelines needs this file in order to run. For information about how to configure the YML file in your repository, check out our documentation. If you're still having issues with pipelines not being triggered, can you…

Hey @nickcub, Thanks for reaching out. Can you please raise a support ticket so that we can look at your repository in more details? Thanks, Aneita

Hey @Bram van Dooren, Thanks for reaching out. Pipelines that are defined for pull requests will run only if there is a pull request open for the branch defined. i.e. in your example above, the pull-requests pipeline will run when a PR is open from the master branch (not when a PR is merged into the master branch). Branch…

Hey @Relaxo, Thanks for reaching out. Can you please raise a support ticket so that we can look at your repository and investigate in more detail? Thanks, Aneita

It looks like there's already an open feature request on our issue tracker. I encourage to vote for and watch that issue if it is something that you're interested in seeing. We'll provide updates on our progress via the issue. 

Hi @Jelle van Oosterbosch, We currently don't have an environment variable for the user who triggered the deployment. However, you can raise a feature request on our public issue tracker if it is something that you'd like to see in Bitbucket. Aneita

Hi Nikolay, We currently have an open feature request to display better Pipelines usage information. It sounds like your request falls under that. I encourage you to vote for the issue and to add a comment with your use case if it is something that you're interested in seeing. Thanks! Aneita

Hi Varadhan, Currently, artifacts are used for keeping files / preserving state between steps and are not accessible through Pipelines. We do have an open feature request to support this, so I encourage you to vote for the issue, and include a comment explaining your use case for viewing the artifacts if it is something…

Hi Daniel, Can you please create a new issue with the component as 'Pipelines' on our public issue tracker and include a comment explaining your use case for the repo name as an environment variable? This will help us to keep track of this feature request. Thanks, Aneita

Hi Raymond, Can you please include a screenshot of what you see in your Pipeline? Test results will only be displayed in the UI if there are test failures. If all of your tests pass, you will not see anything in the UI. If there are test failures, then you will see something along the lines of '5 / 20 tests failed' against…

Hi Sydney, Pipelines is built so that you get fast, continuous feedback on changes to your repository and ideally, Pipelines should be running every time you push to your repository. However, if you only want your pipeline to run when manually triggered, you can configure your pipeline as a custom pipeline. This allows you…

Hi Jie, We recently fixed a bug that caused Gradle test logs to not render properly in the UI. Can you please check whether you are still experiencing this problem? If you are, please raise a support ticket so that we can look at your repository in more detail. Thanks, Aneita

Hi Robert, Can you please raise a support ticket so that we can look at your repository and pipeline in more detail? Thanks, Aneita

Hi Gabriel, There currently isn't a way to prevent scheduled pipelines from running on the same commit. We do have an open request to improve this. I encourage you to vote for that issue and add a comment with your use case if it is something that you would like to see. Thanks, Aneita

Hey there! The Deployments feature is in alpha at the moment, and only available to alpha customers. Are you part of the Bitbucket Pipelines Alpha group? If not, you can sign up here.

The official Julia Docker image has the required tools for testing. See the official Docker image. You can configure Pipelines to use this image using: image: julia:latest For more info on using a custom image, see the documentation. 

If you are currently using the Google Apps integration, and don't have group-based syncing yet, you will receive an email from Atlassian in the next couple of weeks asking you to migrate to group-based syncing. If you are not currently using the Google Apps integration, group-based syncing will be available to you within…

With group-based syncing, you can select Google Apps groups to sync and users belonging to those groups will be synced to Atlassian Cloud. While you can't select specific users to sync, you can achieve the same end result by having these users in a group which is synced.