Philip Hodder Atlassian Team

Hi Suleman, First, you'll need to set up a bot account that is able to have write access to your repositories from Pipelines: https://community.atlassian.com/t5/Bitbucket-questions/Problem-getting-BitBucket-Pipelines-to-commit-back-version/qaq-p/760022#M29587 Once you've got that working, you can run the necessary git…

Hi Jaro, Can you open a support ticket here: https://support.atlassian.com/contact/#/ We'll get things fixed up for you. :) There's some authentication that we'll need to be do between pipelines and your new webhooks. Out of curiosity, why did you want to edit the Pipelines webhooks? Thanks, Phil

Hi Greg, Is there anything of interest in the logs of your Samba service container? Do you need to specify any specific ports when running ldapadd, or do the defaults match with what samba is using? I can't see any reference to samba in the output of 'nmap'. Is that expected, or should it be there? Thanks, Phil

Hi Samuel, What is the location of your Dockerfile? The error is indicating that Docker can't find a Dockerfile in the current directory. If you need to specific the path of the Dockerfile, you can use the `-f` flag docker build -f <path_to_docker_file> -t us.gcr.io/$GCLOUD_PROJECT/$IMAGE_NAME:$IMAGE_TAG . Thanks, Phil

You're welcome! :)

Hi Aazib, If this is still an issue for you and causing you issues, you can open a support case here for further investigation: https://support.atlassian.com/contact/#/ Thanks, Phil

Hi Mykhailo, If you'd like to create a custom script, you could add it as a part of your branch defined Pipelines. For example: pipelines: branches: feature/*: step: script: - ./build-and-test - ./lint-all-code # i.e. If code is poorly formatted, then fail the build. - ./verify-master-is-up-to-date master: step: script: -…

Hello Julio Your current definition will only copy the node_modules directory. Not the contents itself. To have the entire directory and its files copied, you can change your configuration to: artifacts: - node_modules/** The other issue is you have the node cache enable on all your steps, which caches the same directory.…

Hi Aazib, Is this still occurring for you? Bitbucket was encountering a high error rate yesterday, which may have affected you. Details are here: https://status.bitbucket.org/incidents/x2bdsx6v7l9z Thanks, Phil

Hi Mykhailo, The merge checks feature is customisable. Here's an example, where I've restricted writing to master only via PR, where only I can merge the PR, and when it has satisfied the other criteria: I'm unaware of any free trials for Premium. But you can try out this feature already, on any plan. You won't be able to…

Hello Ahmed, When you see the message "you can only edit the head of a branch", it means you're trying to edit a file that has already been updated. So you need to go to the latest version of that file to edit it there. If the yml file was not included in the clone/pull, then it's likely that it exists on a different…

Hi Damian, Currently, the only Pipelines concurrency limitations are available for Deployment Concurrency. There is no general concurrency control on other forms of pipeline. If you'd like, you can open a feature request with a description of your use-case. Thanks, Phil

Sorry for the delayed response. Some other workarounds to not have the secret in your image layers If you're able, you should perform the dependency downloads outside of your Docker build and COPY them into your build instead. That will prevent this issue entirely. You are also able to run commands that would clean up the…

Hi Sean, Try this: clone: depth: 5 # or some other number of commits. You can also configure 'full' if you need the entire commit history. pipelines: ... # standard pipelines stuff from here Look here for more…

Hi Patrick, I suggest you open a feature request relating to this specific issue. As we have no built-in way to configure the line endings, on clone, at the moment. As a workaround you'll need to manually change the line endings as part of you build. This bash program, unix2dos, here seems to be useful in this case (I…

Hello Christian, The caching behaviour you see there is specifically for downing the Gradle binaries. What Docker image as your using for your build environment? Does it have Gradle installed? You can check by running 'which gradle' as the first command of your build. You may need to use a different Docker image for your…

Hi Mourya, We have no plans to integrate Bitbucket Pipelines with Bitbucket Server. We have focused Bitbucket Pipelines feature set, as well as our architecture, on integrating with Bitbucket Cloud. For Bitbucket Server customers, we recommend you use Bamboo Server as your CI/CD tool. Thanks, Phil

Hi Kamran, The SSH UI does not add the public key to your SSH server. You need to do that manually. Add the public key in the UI to the "~/.ssh/authorised_keys" file on your server. Thanks, Phil

Hi Max, Can you try do a quick check that the connection works: <span>$ ssh </span><span>-</span><span>qT user@downhost exit$ echo $</span><span>?<br>// Should be 0</span> Your user may not have permission to modify files, so it'll be good to remove that factor first. If you get a 0, then double check the permissions of…

Hi Hiren, The issue you're encountering is due to the YAML language spec. ": " (specifically with a space) will turn the command string into a map instead. You can use quotes around the command to ensure it's a string. Though this may still have some issues. This will fix the parsing issues. But may still fail in your…

I can see it now. Probably a caching issue on my end. I can double check with the team, but I'm pretty sure the user-defined Docker cache is naive and uploads all image layers it finds. This would include all stages in a multi-stage build (as it's beneficial from a caching perspective). The volumes of the containers are…

Ah. I see now. :) A service container is typically used as something like a separate process. Such as a database or queueing mechanism. The 'docker' is a bit special (mainly due to security requirements on our end), which may have confused you. Can you try this configuration instead: image: microsoft/azure-cli:latest…

Can you try adjusting the spacing of your bitbucket-pipelines.yml to this instead: definitions: services: mydeploy: image: microsoft/azure-cli:latest memory: 6104 options: docker: truepipelines: default: - step: services: - mydeploy # Indented this line. size: 2x script: - az --version

Hi Charles, Can you go to a pipeline result page and hover your mouse over the service name? You should see something like this: Check that matches with what you've defined in your bitbucket-pipelines.yml. Thanks, Phil

Hi, Can you please add in some of the error messages you're seeing? We can look in more detail afterwards. :) Thanks, Phil

Hi @Jonathan Little, I received an email notification that you replied here, but I can't see it on this page. Can you try reposting your reply for me to see? Thanks

Hello Alessandro, Currently service environment variables have to use literal strings. We have a page with the current limitations with service containers. A work around would be to use Docker to manually spin up your service containers as part of your pipeline. Then you can explicitly set the environment variables with…

I'd recommend you have the same btibucket-pipelines.yml configuration on each branch. So on *all* your branches, you can have something like: pipelines: branches: master: - step: script: - # deploy to prod heroku graphql: - step: script: - # deploy to staging heroku default: - step: script: - # run any other pipelines…

Can you double check if there's a bitbucket-pipelines.yml file on the 'graphql' branch, and what the configuration of it is?

Can you double check that Pipelines is enabled? Repository Settings -> Pipelines -> Settings You may also be out of build minutes. You can check that on the main Pipelines page: