Philip Hodder Atlassian Team

Hi Pavlos, Can you add an example bitbucket-pipelines.yml script so we can check everything is configured correctly? Can you also have a look at your Repository Settings -> Pipelines -> Pipelines Settings. This will show if Pipelines is enabled or not. If it's enabled, it should look like this. Thanks, Philip

Hello Dominik, We currently don't have support for either of the artifact features you'd like. We have an open feature request to prevent artifacts from downloading in certain steps: https://bitbucket.org/site/master/issues/16728/ability-to-prevent-a-step-from-downloading I've added a (private) comment with a link to this…

Hello Gnanamadhu, We have an internal Dockerhub Mirror which caches *public Dockerhub images* inside of our build cluster. So docker pull times should be shorter on subsequent pipeline runs. You will still need to run Docker pull as each step is ephemeral, so the Docker image will not be present in your step by default. If…

Hello Alexandr, Pipeline Services are not exposed by the Docker Daemon, which is why they are not showing in `docker ps`. What are you trying to do? If you're trying to just interact with the database normally, then you should be able to use a normal Postgres client (such as psql), as the necessary ports are already…

Hello Chris, We have two separate Docker caches. One is the "caches" definition in the YAML. This is primarily used for caching Docker images you are building. However, it will also act as a cache in your repository for images you pull. However, this cache is limited to 1GB, so it may not be large enough for images. We…

Hello Roman, Currently Bitbucket Deployments only supports having the three environments: test, staging, and production. We are currently looking into adding support for more environments. You can follow this feature request to get updates as they happen. Thanks, Phil

Hi John, I'm not sure why this is localised onto a specific branch, but this looks like an apt-get issue that we discuss a work around for here: https://community.atlassian.com/t5/Bitbucket-Pipelines-articles/Bitbucket-Pipelines-Apt-get-update-returning-404/ba-p/1042290 In your instance, I think you can try updating your…

Hmmm. I can't seem to reproduce this. Here's what I'm doing. Maybe something stands out as different to you? I have the following bitbucket-pipelines.yml on my master branch. pipelines: branches: test*: - step: script: - echo hello I then click on the Branches sidebar icon. And then 'Create Branch'. I call the new branch…

Hello, As far as I understand this already happens, assuming that the branch has a bitbucket-pipelines.yml. Can you paste in an example of your bitbucket-pipelines.yml? Thanks, Phil

Hi Pawel, As you noted, there is currently no environment variable to indicate which user triggered a pipeline. We have an open feature request to add this as an environment variable: https://bitbucket.org/site/master/issues/14006/environment-variable-for-user-who For the time being, you could perhaps look at the author of…

Hi Pawel, At this stage there is no information provided in Pipelines that indicates the user that triggered the pipeline. We have an open feature request to add this an environment variable: https://bitbucket.org/site/master/issues/14006/environment-variable-for-user-who For the time being, you could perhaps look at the…

Hi Justin, Is this still occurring? Can you run "ls" at the start of your build to see if any of the repository contents are in the build directory? If there are no files, can you open a support ticket? Thanks, Phil

Hi Serhii, What Docker image are you using? It looks like the image may no longer container gcc, and that you'll need to install it manually in your build now (or create a new image with it already installed). Thanks, Phil

Hello Jowan, Currently only the username, password, and email support environment variable values. The image name does not support having environment variables. If you'd like, you can open a feature request to support this here: https://bitbucket.org/site/master/issues/new Depending on what you're doing, you could…

Hi Joshua, I'm not sure if you can interleave anchors and other items into the YAML like that. If you remove the hello world before and after your myCommonScriptLinesAnchor then it will work fine. As far as I can find, there isn't a way to merge arrays in YAML using…

Hello, Docker images based off Debian Jessie no longer perform apt-get update successfully. We have full details documented here: https://community.atlassian.com/t5/Bitbucket-Pipelines-articles/Bitbucket-Pipelines-Apt-get-update-returning-404/ba-p/1042290 You can likely just upgrade your Docker image to a new version to…

Hi Micha, YAML parses the ': ' (colon immediately followed by a space) as a map. Which breaks the parsing we expect (a string). To working around this, you can either Place the entire command into a string: default: - step: caches: - node script: - 'echo "{\"infuraKey\": \"$INFURA_KEY\"}" > infura-key.json' - npm i…

Hi Omarlo, Can you try using the "run-as-user" property. This will allow you to be a non-root user in Pipelines. For example image: name: <your image name> run-as-user: 1000 # Your normal pipeline below pipelines: default: - step: script: - echo Hello Thanks, Phil

Hi Petar, Yes, that's expected. We persist the branch history of Pipelines, even if the branch (and its associated commits) has been deleted. As those pipelines may have done things that need reviewing later in the future. Thanks, Phil

Hello Jonathan, You may find Deployment Variables helpful here. You can set up a different value for a variable to run on deployments to different environments. For example: pipelines: default: - step: deployment: test script: - ./deploy-to-env $PROPERTIES_FILE # Set to dev.properties - step: deployment: staging script: -…

Perhaps you can see if adding Deployment Permissions to the production deployment. You'll be able to set up a deployment step for production which can only be triggered by repository admins.

Hello, It seems like the php image you're using was updated to no longer include git. You will now need to either create a new image with git installed, or install it as part of your build. apt-get update && apt-get install -y unzip git Thanks, Phil

Hi Michael, Last week, we released the ability to rename tracked environments to Pipelines alpha customers. This is the first step towards allowing flexible deployment environments, and we're now working on allowing users to add more environments to track. We hope to have this functionality available to our users by…

Hi Michael, Sounds like a good idea. It's a decent journey through the UI to trigger a pipeline. One alternative way to trigger a manual pipeline (although still jumping through several pages), is the Commits page -> Select the specific revision -> Select "run pipeline for the commit" -> Select config -> Run.…

Hi Harendra, For the builds to show in the UI of Bitbucket, the CI provider has to post an update to the Bitbucket Build Status API. I'm not sure if Azure Pipelines does this automatically. So you may need to open a feature request with the team, or manually do it as part of your Azure Pipeline build. I'm not familiar with…

Hello, What Docker image are you using for your build? Perhaps that has been updated to not include git anymore? Can you try rerun an old successful pipeline and see if that still works? Thanks, Phil

Hi, This is a known issue with some Docker images. I've posted full details of this (and workarounds) here: https://community.atlassian.com/t5/Bitbucket-Pipelines-articles/Bitbucket-Pipelines-Apt-get-update-returning-404/ba-p/1042290 Thanks, Phil

@Robert's approach looks fine here. (FYI: The GitHub issue URL is linking to a search query, not the URL you intended: https://github.com/nodejs/docker-node/issues/1013) There's a PR currently open which means you won't need that workaround for too long. If you need to keep using Jessie repositories, then there's some…

@[deleted] at this stage I recommend you use our Slack Pipe inside of an after-script.

Was there any error message on the Pipeline Result? (It should be under the 'Failed' or 'Error' icon) Otherwise, we should readd it. As that used to be in the UI to surface these types on these issues. :)