Jeroen De Raedt Atlassian Team

Hi @Bill, try this: pipelines: branches: "(feature-*|hotfix-*)": - step: ...

Hi @Decebal Dobrica, you might want to take a look a custom pages: https://confluence.atlassian.com/bitbucket/caching-dependencies-895552876.html (see the 'Custom caches for other build tools and directories' section). This allows you to define custom caches. You could then combine this with different pipelines for…

Hi @Eyal Lapid, with the current branch pipelines that is not available. However, the upcoming pull request builds will have this information available as a branch variable. You can track to progress of this work here: https://bitbucket.org/site/master/issues/13438/add-specific-pipelines-configuration-for (should be…

Hi @Heiner Oßwald, unfortunately at the moment there is no way to skip the clone. Please feel free to raise a feature request here: https://bitbucket.org/site/master/issues/new 

Hi @Steven-Pi, as the log suggests, maybe try running apt-get update This might update outdated dependencies first. 

Hi @Arkady B, Try this: https://api.bitbucket.org/2.0/repositories/username/repo/pipelines/?sort=+created_on

Hi @sonjaya sonjaya, there are multiple ways to deploy to AWS EC2 using Bitbucket Pipelines. The easiest might be through AWS CodeDeploy. There is an excellent tutorial here: https://hackernoon.com/deploy-to-ec2-with-aws-codedeploy-from-bitbucket-pipelines-4f403e96d50c

Hi @pingpong_mikaels, at the moment there is no built-in wallboard functionality in Pipelines. We have an open feature request which you can track here: https://bitbucket.org/site/master/issues/12765/pipeline-wallboards There are some tips on there that might be of help. 

Hi @TragicDog, I am not so familiar with Hugo, but I found these articles on using Pipelines with Hugo: * https://gohugo.io/hosting-and-deployment/hosting-on-bitbucket/ * https://www.aerobatic.com/blog/hugo-bitbucket-pipelines/ * https://www.bitquabit.com/post/automating-hugo-deployments/ *…

Hi @Mariya, you can use $BITBUCKT_REPO_SLUG A full list of environment variables can be found here: https://confluence.atlassian.com/bitbucket/environment-variables-794502608.html

Hi @Ian Williamson, it looks like you disabled Pipelines on your repository, so I can not check the output of your tests anymore? Googling a bit for your first error brought me to https://github.com/ansible/tower-cli/issues/579 - which suggests that you need to login with the tower cli first. However, I don't see this…

Hi @Ian Williamson, in your tower.bash script I see that you configure for example $hostval like this: hostval=$(tower-cli config host $host) This probably doesn't return the value that is used for the host as you think it does. It just results in capturing the log output of the `tower-cli config host $host` command -…

This looks like an issue with google Cloud, or at least your configuration of it, rather than something relating to Bitbucket Pipelines. Take a look at these tips: https://github.com/GoogleCloudPlatform/nodejs-getting-started/issues/153 

Hi @Philippe Guilbault, this is a know limation of Pipelines at the moment. If you would push a new commit to your repository, this should fix the issue for your repository. Let me know if this helps?

Hey @Duarte Aragão, I check your repository, and it looks like you managed to resolve it? 

Hey @Derektar, This is certainly possible. You basically have to configure to which maven repositories your Pipelines builds have access to. In order to achieve that, you have to configure the maven servers you want to access: https://maven.apache.org/settings.html#Servers There are a couple of different ways to accomplish…

Hey @Naiyin Tan, the build number gets injected as an environment variable into you build as `$BITBUCKET_BUILD_NUMBER`. So for example, you could execute something like this: <span>gradle </span><span>-</span><span>Pversion</span><span>=</span><span>$BITBUCKET_BUILD_NUMBER</span><span> publish</span>

Hey @Mikk3lRo, I am not entirely sure what the root cause is of this. If you think that you might be able to get it to work by specifying the `docker run` command, you could try this from within your build. As part of the build, just execute `docker run <your-image> <your-params>` and see if this works. 

Hey @ffmit, you installed git in your first step - whereas it is actually needed in your second step. Try updating your second step to: - step: # set HEROKU_API_KEY and HEROKU_APP_NAME environment variables # set clone `depth: full' as described here: https://confluence.atlassian.com/x/Y9-5Mw name: Deploy to Heroku…

Correct, these ones: https://confluence.atlassian.com/bitbucket/environment-variables-794502608.html You declare them in the Pipelines UI, and they will be made available as environment variables. 

Hi @David Cano, unfortunately the formatting here is not ideal (since YML is whitespace sensitive). Would you mind create a snippet and share a link here? 

Hi @Erfang Chen, the approach that you describes sounds like a sensible thing to do. By creating your custom optimised image, you won't lose time installing dependencies on run time and thus make your overall build time smaller. I am not sure if you are planning to also put JFrog credentials in your settings.xml file - but…

Unfortunately not, you can only configure it the bitbucket-pipelines.yml file: https://confluence.atlassian.com/bitbucket/configure-bitbucket-pipelines-yml-792298910.html#Configurebitbucket-pipelines.yml-ci_max-timemax-time But feel free to raise a feature request: https://bitbucket.org/site/master/issues/new 

Hi @Foster, Pipelines shouldn't be downloading any such files. Since it is in your build directory, I suspect that something in your build is responsible for downloading or generating this file? 

Hey @dervisc, the easiest way would be to use Pipelines services: https://confluence.atlassian.com/bitbucket/use-services-and-databases-in-bitbucket-pipelines-874786688.html You can specify the Docker service (based on a Docker image that runs your app), and let your main build execute Selenium tests that call out to this…

Hi @Leio Heyenrath, I suspect that the maven artifact has been removed (which can happen since it is only a BUILD-SNAPSHOT). Try switching to one of these versions: https://mvnrepository.com/artifact/org.springframework.boot/spring-boot-gradle-plugin 

Hey @ffmit, this is most likely because the git client is not installed in the Docker image that you are using (php:7.1.3). You can either look for a different image that has git installed, or try installing it (e.g. through `apt-get install git-core` as the first command of your script). 

Hi @Pavinthan, take a look at this documentation page, where it outlines some examples how how to set up pipelines per type of branch: https://confluence.atlassian.com/bitbucket/branch-workflows-856697482.html

Hi @Anton Popov, remove any existing pipelines you have from your bitbucket-pipelines.yml, and take a look at https://confluence.atlassian.com/bitbucket/scheduled-pipelines-933078702.html

Interesting use cases, and certainly something we can consider. To make it easier to track, and for others to watch and upvote this feature request, please raise a ticket here: https://bitbucket.org/site/master/issues/new Thanks!