Philip Hodder Atlassian Team

Hi George, Looking here (https://stackoverflow.com/questions/22463614/php-artisan-migrate-throwing-pdo-exception-could-not-find-driver-using-larav) it seems you may also need to install php-mysql into your container with apt (I'm not sure on how docker-php-ext-install interacts in this context) Try adding apt-get install…

Hi Aaron, Have you got any specific error messages we can work off? This seems like it's an authentication problem? If you already use Heroku on your local machine then you should be able to copy over the script commands you use with the appropriate auth set up. If you haven't gotten that set up yet locally, it'll probably…

Your YAML is slightly incorrect. It should look like this instead: image: ubuntu:16.04 pipelines: default: - step: script: - apt-get update -y - apt-get install -y git - git clone <your_repo_here> # For example, git@bitbucket.org:username/repo-2.git You were missing the "script" section. :) You shouldn't need to do all…

Hello, This answer is based on what I found here: https://askubuntu.com/questions/384677/how-do-i-install-and-enable-pdo-mysql-and-gd-extensions-for-php5 So it may not be correct (I'm not a PHP developer) It looks like you need to change your apt-get install command to instead be: $ apt-get update && apt-get install -y…

Hi Greg, To set up tag builds, you don't need to specify the branch the tag is from. So you can set up a tag build off of 1.2.3-rc.1 like this, for example: pipelines: tags: '*.*.*-rc.*': - step: script: - echo "My tag build" You should also be able to shorten this if you're just interested in release candidate builds:…

Hi Rob, How have you set this up locally? You should be able to reuse your composer.json file if it works in a similar way locally. Or maybe there was some set up you did when you first installed composer on your machine that you need to redo in Pipelines. Do you run into any specific errors that don't surface locally when…

Hi Yury, Currently there is no way to pass parameters to a pipelines build in the way you're describing. We have a feature request you can follow here: https://bitbucket.org/site/master/issues/13737/parameterized-builds It'd be helpful for us if you added a comment with your specific use-case there. Can I ask why…

Hey Daniel, Can you try start fresh with these instructions. https://confluence.atlassian.com/bitbucket/use-ssh-keys-in-bitbucket-pipelines-847452940.html Manually setting known_hosts and SSH keys as part of your pipeline build is quite a pain to get right. We've got some features above that should hopefully make that a…

Awesome! :D

Hmmm... I've set up a repo here testing this. Does this look like the correct behaviour to you? I've created multiple tags against a commit that already exists and pushed them with "git push --tags". Is that the same thing you're trying to do? Repo: https://bitbucket.org/phodder/push-tag-test/addon/pipelines/home#!/ If…

Hi Bryan, Unfortunately a kludgy workaround is indeed currently needed. Here's the steps to get repo push-back in Pipelines working. * Set up a Pipelines SSH key as specified in Step 1…

Right. I think all the documentation here may be relevant for you then: https://confluence.atlassian.com/bitbucket/use-ssh-keys-in-bitbucket-pipelines-847452940.html If you're trying to deploy files to your production server, you'll probably not be using Git. You'll need to set up an SSH key and then maybe use SFTP or a…

This is still a valid answer to the question. But I've unaccepted this to highlight the new SSH key setup flows.

04/04/2018 update We've updated the SSH functionality in Bitbucket Pipelines, and I would suggest you following the documentation here: https://confluence.atlassian.com/bitbucket/use-ssh-keys-in-bitbucket-pipelines-847452940.html The responses here are still valid, but are much more complicated to set up than the above…

Hi Daniel, It looks like you've found some old Community questions. Sorry, we've forgotten to keep these responses up to date. If you tell me what you're specifically trying to do I can give you a more catered answer. I've posted an updated response…

Up to date as of 04/04/2018. For example. I want to clone repo-2 into a build from repo-1 To use SSH to clone another repository from Bitbucket you need to do the following. * In repo-1 generate a Pipelines SSH key to be injected into your build container. Follow Step 1…

Hi Janne, Can you paste in an example of your configuration? I got one behaving the way you want with the following configuration: pipelines: branches: '*': - step: script: - echo "A branch push build" tags: release-*: - step: script: - echo "A tag triggered build" The tags section will build on any pushed tags that start…

Hi Christian, Currently Pipelines does not have a per-branch restriction on rerun triggers. We have a related feature request you can follow here: https://bitbucket.org/site/master/issues/13676/ability-to-restrict-who-can-run-deployment You can add your use case there to help our PMs prioritise the feature. Thanks, Phil

Hi Tom, While that is valid YAML, the Pipelines validator is set up to verify YAML that strictly follows the definitions we provide in our documentation here: https://confluence.atlassian.com/bitbucket/configure-bitbucket-pipelines-yml-792298910.html However, our backend parser supports generic YAML so you're references…

Hi Aleksandra, Can you copy in the error logs you're seeing? The StackOverflow post you found doesn't seem to be related in this case. As that is in the context of *building* a Docker image, instead of Pip errors running inside of a Docker container. Do you have any dependencies that require special auth to access? Have…

Hi Jasper, When you are running this locally, are you running this inside of a Docker container? This seems like it could be a dependency / configuration problem, where your local environment will already be setup correctly. Try following this guide to run this build in a local Docker…

Hi Alasdair, You can define a custom Pipelines cache by following the instructions here: https://confluence.atlassian.com/bitbucket/caching-dependencies-895552876.html Thanks, Phil

Hi Balu, Can you run 'whoami' at the start of your script to verify the user you're running as? It should be defaulting to root. If it's not running as root, you can add the following to your yaml to run as root. # The important stuff image: name: normal-image-you-use run-as-user: 0 # Everything below doesn't matter.…

Just adding that we've got a simpler process for using SSH keys now. Try looking at the documentation here, as it might be easier for you to set everything up! https://confluence.atlassian.com/bitbucket/use-ssh-keys-in-bitbucket-pipelines-847452940.html

Hi, Can you verify the *full path* for the volume mounting? Is the full path actually "/host_mntC/z_copied" or is it a subdirectory of other directories? From the docker CLI documentation: When the host directory of a bind-mounted volume doesn’t exist, Docker will automatically create this directory on the host for you. In…

Alternatively, for anyone using an image that doesn't have yarn installed you can also install it as part of your build. For example, add an installation command to your script such as: - npm install yarn

Hi Stuart, Instead of using Service containers for OpenVPN clients, you can run your own docker containers manually in your build with the necessary CLI options. pipelines: default: - step: services: - docker script: - docker run --cap-add=NET_ADMIN your-image:tag Docker run docs:…

Hi Peter, You can configure your pipeline to run as a user that isn't root. For example: image: name: image-name:tag run-as-user: 1000 # root is always 0. So this will make you non-root. pipeline: default: - step: script: - ./do-the-thing I noticed there seemed to be no reference to this in the documentation, so I've…

Hi Victor, For running and install Bazel, you can do so similar as in a normal Bash environment. You can also use a Docker image from DockerHub that already has Basel installed. There are currently no official Bazel images, so you will need a community created one. Documentation on configuring Docker…

Hi Matt, There's three questions here, so I'll answer them individually. * You can create custom PR conditions using the Merge Checks feature in Bitbucket. On each repository, you can define rules for specific branch PRs. Merge checks docs:…