Philip Hodder Atlassian Team

Hi Carl, When you say you've uploaded a file to the repository Downloads are. Do you mean the downloads section (listed in the sidebar)? If so, these aren't copied into your pipelines. Only the repository itself. You need to manually download these. You can have a look a the REST API docs for how to do this:…

Looks like it didn't find the artifact. Can you run these commands at the end of your build step? cd ~ ls -Rla ls -Rla | grep jar That will list every file in your step. It will also show all files names containing the string "jar". Hopefully that helps.

Weird... Thanks for that, I'll note it down as a potentially separate issue to investigate once the other user namespace issue is fixed.

The workaround I provided above should suffice. It's an issue with file permissions across Docker build instructions. If file modification is in a single instruction then the Docker build should work.

Hi Stefan, I suspect your question may be related to this one: https://community.atlassian.com/t5/Bitbucket-questions/rm-rf-inside-container-via-Bitbucket-pipeline/qaq-p/903061#M33507 Can you try combine all the RUN instructions into a single instruction? Like so: FROM amazonlinux:latest ENV TZ=Europe/Stockholm ## ##…

EDIT: This is scoped to any deletion. Not just symlinks. Hello, The Pipelines team has done some investigation into this, and this issue seems to be happening when the following three conditions are met: * Your account has user namespace remapping enabled. This is currently enabled globally. (This was a security feature…

Hi Miroslav, Bitbucket Pipelines currently does not provide a shell interactive mode. I suggest you open a feature request here: https://bitbucket.org/site/master/issues/new As a workaround, you could try set up a reverse shell with Ngrok. And debug through that instead. Once factor you could also investigate locally, is…

Hi Lenin, In regards to your pipelines/maven script: We've been tracking providing more consistent CPU in this open ticket that you can follow: https://bitbucket.org/site/master/issues/13079/provide-a-fairly-constant-cpu-and-network We've currently fixed several performance problems (such as IO and networking), CPU is the…

Hi Min, Bitbucket Pipelines does not currently support port mapping on services. Your service will use its default port. (In the case of mysql, 3306) As a workaround, you can use Docker Compose to spin up your database container and map it is part of your Docker Compose configuration. You can also add a feature request…

Hi Senthil, Bitbucket Pipelines currently supports the following for Slack notifications: * The status of the entire pipeline (success / failed / first green build). * The status of a deployment step (success / stopped / failed). If you need more fine-grained notifications, then you can open a feature request here:…

Hi Artem, Bitbucket Pipelines currently only supports rerunning failed steps. If it's relevant to you, we have an open feature request to support rollbacks in deployments: https://bitbucket.org/site/master/issues/16604/permit-rollbacks-in-bitbucket-cloud Otherwise, you can open a new feature request here:…

Hi Ekene, Since this is a duplicate question, I'll redirect you (and any future viewers) here: https://community.atlassian.com/t5/Bitbucket-questions/How-to-push-select-files-to-heroku-with-pipeline/qaq-p/899716#U905113 Thanks, Phil

Hi Ekene, I'm not particularly familiar with how Heroku deployments work. However, this StackOverflow question seems to be the exact same question that you have: https://stackoverflow.com/questions/7539382/how-can-i-deploy-push-only-a-subdirectory-of-my-git-repo-to-heroku Does that help at all? Thanks, Phil

Hi Xinchao, Bitbucket Pipelines currently provides no support for sharing bitbucket-pipelines.yml configuration across multiple repositories. We have a feature we're speccing that will allow for sharing scripts across repositories. You can follow it here:…

Hi Selvaganesh, Can you try change your script to: script: - npm install - npm build - npm install -g now # Change this line. - now --token $NOW_TOKEN Some additional context on the '-g' flag: https://stackoverflow.com/a/8951576 Thanks, Phil

Hi Christoph, There is currently no support for displaying the screenshots in the UI. If you're interested in seeing that as a feature, you can open that as a feature request here: https://bitbucket.org/site/master/issues/new If you'd like to download the screenshots from your build, you can mark them as step artifacts…

Hi Nicolas, Can you confirm that the files you need exist in the `sephogate-workflow-approbation-master/build/libs/` directory? Your configuration looks correct, to me. Are there errors in the 'Build teardown' section of your pipeline logs? We have artifact upload information there. Thanks, Phil

Hi Challa, Is this still an issue for you? Can you paste in the bitbucket-pipelines.yml file you have here? Thanks, Phil

Hi Fabian, Pipelines steps will finish with the exit code of the commands being run. So if your step is always passing, it means the command running your unit tests is returning 0 as an exit code. Can you add more details about the commands your running, so we can determine why the exit code is always 0? Thanks, Phil

Hi Andrew, At the moment there is no support for configuring when an artifact is (and isn't) downloaded at a per step basis. A step will always attempt to download the artifacts defined in previous steps. If you'd like, you can open a feature request for this here: https://bitbucket.org/site/master/issues/new Thanks, Phil

Hi Acho, Bitbucket Pipelines runs steps sequentially. So the 'Deploy to Heroku' step will not begin execution until your 'Build and Test' step completes successfully. If any steps fail to complete successfully (e.g. a test fails), then the entire pipeline will stop executing. Have you been seeing different behaviour?…

Hi tuguldur, You can run a shell file in Pipelines. The quickest fix: Change your command to /bin/bash deploy.sh if it fails due to bash not existing, then instead use /bin/sh deploy.sh More detail below: You can check that it is an executable with: ls -l If you're not familiar with Linux file permissions, you just want to…

Brilliant! :D If you remember how you solved the problem, can you note it down here?

Hi @Oleg Sigida Indeed. We don't allow any cap-add flags anymore for security reasons. The only feedback I can offer is to follow this ticket: https://bitbucket.org/site/master/issues/12753/allow-customers-to-connect-the-pipelines We'd like to explore this feature, but have received limited feedback at the moment. If you…

The feature request for Windows/.NET builds is here: https://bitbucket.org/site/master/issues/13452/support-for-native-windows-net-builds-on Follow that ticket for updates from our team.

No problem :)

I think you still need to use the IP range I suggested. The IP mentioned in your build is being added to the known_hosts inside your pipeline. i.e. Your pipelines is talking to Bitbucket to perform the clone (IP 18.205.93.0 in this case) If the range I suggest doesn't work, then try the other ones and report back. :)

Hi @GC, The IP whitelist needs to be configured on your client's account (the one that owns the repository you're trying to clone). Not on your own user account. The IPs that need to be whitelisted are listed…

If we do ever make changes to our log/meta-data retention policy, we'll make sure to send out a bulk email to our users to give them a chance to retrieve the data for themselves. But again, we have no scheduled plans to do so in the foreseeable future. If you're interested, we have a REST API available for accessing this…

Hi Tom, Artifacts: * Expire 1 week after creation: https://confluence.atlassian.com/bitbucket/using-artifacts-in-steps-935389074.html * Each artifact can not be more than 1GB after compression. Caches: * Expire 1 week after creation: https://confluence.atlassian.com/bitbucket/caching-dependencies-895552876.html * Each…