Philip Hodder Atlassian Team

Hi Sascha, Just to confirm (I'm assume from the syntax), this is for a Pipe? Pipelines supports environment variables as parameters for pipes. You should be able to use variables with the following configuration: VERSION_LABEL: $APPLICATION_ENVIRONMENT"_YYYY-mm-dd_HHMMSS_"$BITBUCKET_BUILD_NUMBER Thanks, Phil

Hi Matt, One thing you might want to try is monitoring the process information, to see if any processes are hanging or becoming zombies. The relevant documentation is here: https://confluence.atlassian.com/bitbucket/how-to-generate-support-logs-in-your-pipeline-959288939.html For your bitbucket-pipeline.yml, it would look…

Hello Chris, Can you expand on what these packages are? What are they used for? If they are build dependencies, you can use the caches feature to persist the packages across steps and pipelines. However, they will not be 100% available as the cache expires every week (or on manual deletion). If you mean copying over the…

Hi Illia, Pipelines does not provide the ability to customise the instance type the build is placed on. The only way to set up something similar would be to have a script in Pipelines which would then spin up the instance type you want, and then clone your repository onto the instance and run tests there. Thanks, Phil

Hi Hamdi, The colon character is causing the particular line you have to be parsed as a map instead of a string. This is part of the YAML specification, which the bitbucket-pipelines.yml file follows. Specifically, a colon followed by a space will make the entire line interpreted as a map instead of a string. There are a…

Hi Zemek, Unfortunately not, for the time being. I see you've already started following the related feature request for this. So, I'd say that's the best place to watch for updates on us adding support. Thanks, Phil

From the error message you posted above, it looks like the driver is already installed but has the wrong file permissions. Can you add 'ls -l /opt/atlassian/pipelines/agent/build/drive' at the start of your script and paste in the output you see?

Hello, Can you try add: npm install gulp # install locally to your configuration. At the same time as when you install it globally. (You likely don't need the global version, but leave it in for now just for simplicity) There have been cases, I've experienced, where programs only try to reference the local installation of…

Hi Gabor, You can try use a recursive diff to see the code differences in the repositories. Clone both repositories locally and run the following: diff -r original-repo copied-repo That should show any differences between the two directories. If there are no differences, have a look at the Repository Variables you have set…

Hi Theodore, You can override the default user you are running as, to not run as root. So instead your configuration could look like: image: name: php:7.2-fpm run-as-user: 1 pipelines: default: - step: caches: - composer script: - apt-get update && apt-get install -y unzip - curl -sS https://getcomposer.org/installer | php…

Hi Maxim, Indeed, as you use more features it starts to get a bit more complicated to use Docker to debug Pipelines locally. In regards to environment variables, the best I can offer is to add them in as part of the Docker run…

Hi Celso, Bitbucket Pipelines has a registry cache to speed up start-up times of builds. There is currently no way to refresh the cache (as other users could be using the same image). The best solution I can offer is to update your Docker image with a different tag and then reference the new tag in your…

Hi Zamek, Try following the instructions here: https://docs.docker.com/registry/insecure/#use-self-signed-certificates There may be some additional configuration required, so let me know how it goes. At the moment we don't allow setting Docker daemon flags, but those instructions don't appear to require changing any flags.…

Hi Bharat, Currently Bitbucket Pipelines only supports .NET Core applications. General Windows support has still not been introduced. You can follow this feature request for updates on us adding support: https://bitbucket.org/site/master/issues/13452/support-for-native-windows-net-builds-on Thanks, Phil

Hi Relaxo, If it's in the Assets directory of your project, does that mean it has already been pushed to Bitbucket? If so, the it should already be accessible inside of your Pipelines build container. As we clone the entire repository. If you are already using Git LFS then it will automatically be downloaded to the…

Hi Frederik, You'll need to have SSH available on your FTP server, as FTP only has a limited set of commands available, none of which allow for command execution To use SSH to run commands on a remote server, have a look…

Hi Beatriz, Can you post the full error message you're getting here? That'll help us pin point the issue a bit more. When you tested locally, did you try debugging inside of a Docker container? There may be some settings your machine may already have that fix this…

Hi Rob, At the moment, due to the way the quotes are set, the TEMP_DEPLOYMENT_ENVIRONMENT variable is trying to be retrieved inside of the remote machine, instead of from the pipelines environment. To instead reference the environment variable from Pipelines, the correct way appears to be using double quotes to wrap the…

Hi Tomasz, Can you include some more information about the failing unit test? What's the error, and what is it testing? Is it doing any multithreaded operations? (As we've found this is often a source of inconsistencies in results.) The build script itself runs synchronously. Thanks, Phil

Hi Jan, By default, the build container has 4GB of memory. If you add a service container, each will take 1GB of the total 4GB memory. e.g. 2 service containers. Each service container will have 1GB and the build container will have 2GB of memory. If you'd like to alter the memory usage of your containers, you have two…

Hi Maneesh, Can you paste in a copy of your bitbucket-pipelines.yml file? Can you also try run `ls -l /opt/atlassian/pipelines/agent/build/driver` to check if chromedriver.exe is marked as an executable file? Thanks, Phil

Hi Rabia, You can try use an after-script to print out the contents of these logs. pipelines: default: - step: name: Build and test script: - # Your npm commands<br> after-script: - cat /root/.npm_logs/* Thanks, Phil

Hello Philippe, Pipelines has no built in ability to automatically approve and merge a pull request. You can however use the Bitbucket REST API and call the relevant endpoints inside of your running Pipelines scripts to accept and merge pull requests. The relevant endpoints are documented…

Hi Michael, We have an open feature request for VPN support here. I suggest you follow the ticket here for updates: https://bitbucket.org/site/master/issues/12753/allow-customers-to-connect-the-pipelines Thanks, Phil

Hi, Can you please open a feature request for that here: https://bitbucket.org/site/master/issues/new

Whoops. I missed the question. @Ihor Sviziev not at the moment. I suggest you open a feature request here for us to track: https://bitbucket.org/site/master/issues/new

Can you open a new question with some specific error messages you're getting. Then send me a link to it here. Thanks.

Hi Keith, Currently we do not support having Docker run in experimental mode. You can open a feature request for it to be supported. The Docker team recommends you use multi-stage builds instead of squash to remove intermediate layers. There have also been some discussions around remove the squash flag too. Multi-stage…

Can you try this YAML instead? image: cypress/base:10 options: max-time: 20 pipelines: default: -step: script: - npm install - npm run test artifacts: - /opt/atlassian/pipelines/agent/build/cypress/screenshots/** # Double star provides recursive search. If that doesn't work. Can you take a screenshot of the 'Build…

Hi Robbe, Can you provide a few more steps on how to reproduce your issue? I did the following and everything seemed to work fine. * I created a new team called "testphil' * I created two new repositories called "repo1" and "repo2" * I enabled Pipelines on repo2. * On repo2, I generated a SSH key. * I add that SSH key as…