Philip Hodder Atlassian Team

Hi Ashokaditya, Bitbucket Pipelines provides a bash environment that you should be able to configure in a similar way as locally (with perhaps some environment changes). Perhaps you can include some information about how you build and test these apps locally? (Specific commands/scripts would be preferred here) If you're…

Hi Saharsh, Currently there is no way to configure Pipelines to display code coverage reports like our Test Report viewer. The best work around we have at the moment is to publish them externally, e.g. to AWS S3, then link the URLs to the Bitbucket Build…

Hi Jie, When you're testing your code locally, as you running it inside of a Docker container? All builds in Pipelines are run inside of Docker containers, so perhaps there is an environment dependency that isn't installed on your build environments. There are instructions here on how to run an environment similar to…

Hi Sohail, Currently Bitbucket Pipelines only has support for .NET Core builds. We will soon be looking into supporting general Windows builds (including more of the .NET ecosystem) in the future. You can follow the progress of this feature…

Hi Steve, There's currently no way to configure pipelines to fail on *specifically* cache download errors. You could technically check to see if the cached directory exists, but this will become problematic once your cache expires (as then your build will consistently fail). Thanks, Phil

Hi Victor, Bitbucket Pipelines has no built in way to distinguish *who* triggered a pipeline. The best suggestion I can make is to extract the Git commit author and use that to map to an S3 environment. For example: git show -s --format='%an' You may be able to extract other information from Git which may be more useful…

Hi Simon, Is this still happening for you? Can you attach a copy of your bitbucket-pipelines.yml configuration here? This looks like a bug that we might need to investigate in more detail. Can I get you to open a support ticket so we can get access to your account/repository for further…

Hello Lucas, Currently there's no way to share steps between pipelines, so you'll need to define duplicate behaviour in each pipeline. For example: pipelines: branches: production: - step: name: build & test script: - ./build-app - ./run-tests - step: name: Deploy to production script: - ./deploy-to-production staging: -…

Hi Milosz, You can truncate the BITBUCKET_COMMIT variable inside of your pipeline script. For example: pipelines: default: - step: script: - export BITBUCKET_COMMIT_SHORT=$(echo $BITBUCKET_COMMIT | cut -c1-7) - ... You can see other examples of how to do this…

Hello, Do you have the following in your bitbucket-pipelines.yml? options: docker: true If so, that is the cause of what you're asking about. As that will always include the Docker service in all your steps. Defining a docker service is now sufficient to load it into the step. More information…

Hi Yury, Currently there's no BITBUCKET_DEPLOYMENT type environment variable. Is there any reason that you cannot hard code this inside you're step scripts, given that you already need to specify the environment name on the step? For example: pipelines: default: - step: name: Deploy to test deployment: test script: -…

Hi Daniel, I've opened an internal bug report. As I get the same issue when I use your XML. Thanks, Phil

Excellent! Let me know how it goes.

No problem. I'll pass on your feedback to the rest of the team. :)

Daniel, Can you check to see if this is still an issue for you? We've fixed some bugs in our parser that appear to make your XML parse properly now. I've checked the previously submitted XML files and they all now parse successfully in our parser. Thanks, Phil

Nothing immediate. I'll look into that now.

Hi, At the moment we're only showing full results of failed tests. Can you check that you see them when you have failed tests? Is there anything in particular you'd be interested in seeing when all your tests have passed? Thanks, Phil

Looks like the XML isn't being parsed correctly. What build tool are you using? Are you able to show me the XML that is being output?

Hi, The Test Result view will be shown by default if you have failed tests + failed pipeline. However, it looks like a bug that you can't navigate to the tests even though you have failures (but a green build). I'll open an internal ticket to fix this. Thanks, Phil

Hi, What do you see in the logs for the Build Teardown command? Are any tests being discovered? Which directory are the tests being output to at the moment? We only check for reports in certain directories. Have a look at the documentation here to double…

What error message are you getting? Key not found, or authentication errors?

The keys are injected into your build and should be available to commands that need them (in a similar way to how it would run locally). Note that you'll still need to add the corresponding public key to whichever service you're trying to contact.

If you want to follow @slmt's answer you can also check the BITBUCKET_BRANCH environment variable in the pipeline. https://confluence.atlassian.com/bitbucket/environment-variables-794502608.html Alternatively, you could set up a pipeline that runs on master only and has manual steps that do the deployments. i.e. Steps that…

Hi @Sandeep Srinivasa, Why is SSH not an option? Is it acceptable if SSH is run on every commit/merge as part of the pipeline script? We have some documentation on setting up SSH commands inside of you pipeline here: https://confluence.atlassian.com/bitbucket/use-ssh-keys-in-bitbucket-pipelines-847452940.html Does that…

Hi@Rafal Janicki , Just to follow up. We had an issue where we weren't supporting mounting subdirectories of BITBUCKET_CLONE_DIR. You should now be able to mount subdirectories of BITBUCKET_CLONE_DIR. Thanks, Phil

Hi @DmytroS, We've implemented subdirectory support now. It should work as you initially expected now. :) Thanks, Phil

No worries. I'll pass on the feedback. :)

@Jason Sheedy Using an academic account is unlikely to be the issue here. It looks like you just have your log view expanded. Do you have an icon that looks like this on the top right of your screen? Larger screenshot here. Look at the top right (next to 'Download raw'): If so, when you click it you should see what I'm…

@Jason Sheedy Sorry, I just showed a subset of the page. Here's the whole result: The same view as you're looking at. Thanks, Phil

Hi @Jason Sheedy, Were you previously seeing failed test results as well? Or have none shown? If you have everything already set up, they should be showing on the step like so: If you don't have it set up, you should have debugging information about this in the 'Build Teardown' section of your pipeline. Note there was a…