Comments
-
FYI we saw the recovery of our internal services start from 09:25 GMT October 3 2025. We've seen no signs of unavailability since. Thanks for your patience while we worked through this event.
-
See also https://support.atlassian.com/bitbucket-cloud/docs/bitbucket-pipelines-faqs/#If-I%E2%80%99ve-pushed-a-Git-annotated-tag-in-my-Pipeline-step--why-can%E2%80%99t-I-retrieve-it-in-a-subsequent-step
-
For updates please follow BCLOUD-16995
-
Does this help? i.e. `zip -e /tmp/html.zip .` This will, however, zip up your .git directory. You could try putting the files your want in a subdir and zipping it: mkdir build cp -a stuff build (cd build && zip -r /tmp/html.zip .) ...
-
I think you are having the same problem as this person: https://community.atlassian.com/t5/Bitbucket-Pipelines-questions/Pipelines-quot-scp-deploy-quot-puts-everything-in-quot-build/qaq-p/1074894
-
Look for the answer to the question Can I commit without triggering the pipeline? on the Bitbucket Pipelines FAQ - put "[skip ci]" into your commit messages to have them not trigger builds in Bitbucket Pipelines
-
Good idea, but unfortunately, this is just how it works in Slack - they use the webhook url to define which channel the message is for. Nothing we can do on our end.
-
You have set <span>LOCAL_PATH:"/Users/jhorning/Sites/dev.jtcc.edu/"</span> When it should probably just be LOCAL_PATH: "dev.jtcc.edu" (i.e. the path relative to your checkout that you want to ftp). There is no <span>/Users/jhorning/Sites/dev.jtcc.edu/ in the build when your Pipeline runs.</span>
-
Hi Constantinos, The Pipe is not intended to be used with a zip file already in S3 - the S3 bucket is merely the intermediate storage for the artefact you generate and zip up within Pipelines. you then upload_only it and use 1 or more deploy-only pipes to push that artefact to different environments.…
-
Hi Sunny, `$(pwd)` is resolving to `<span>/opt/atlassian/pipelines/agent/build` so sftp is taking that path and copying everything to your remote, i.e. /opt/atlassian/pipelines/agent/build/wibble gets copied to /var/www/html/build/wibble. If you change `$(pwd)` to `.` I'm guessing it will then copy ./wibble…
-
The atlassian/aws-elasticbeanstalk-deploy pipe takes your zip you have built locally, and can work in 3 modes: * use the command upload-only to upload an artifact to S3 and create a version * use the command deploy-only to deploy an already created version to an environment * with no command , do the upload and deploy in…
-
Hi Eric, Thanks for the corrections! Even if you don't have permissions to write to the repo, you should still be able to see the "edit" button when viewing files e.g. https://bitbucket.org/atlassian/aws-elasticbeanstalk-deploy/src/master/README.md When you try to commit, Bitbucket will fork the repo for you and create a…
-
The docs section I linked shows how to store a key in a secure repository variable and then use a code fragment in your step to save it to a file and use it in your scripts. You can use the same approach for other keys, not just ssh keys. e.g. if you take your key and run (on linux) keys/server.keybase64 -w 0 < then store…
-
Don't check the key into the repository - it will be in the history forever! Instead, use the same approach we recommend for additional ssh keys. See the section entitled Use multiple SSH keys in your pipeline in https://confluence.atlassian.com/bitbucket/use-ssh-keys-in-bitbucket-pipelines-847452940.html
-
I haven't tried it, but .git has directories in it, so wouldn't you have to also exclude .git/*/* and maybe even .git/*/*/* - which sort of doesn't make sense. Have you tried just `--exclude .git`?
-
Ah, now I get you - I didn't follow that it was `eb init -p docker` - I don't know if there is a way to do this - you might need to ask in a awsebcli forum. A workaround would be to substitute the variable straight into your Dockerfile inside pipelines before calling `eb init` - e.g. `sed -e 's/<ENV>/${ENVIRONMENT}/'…
-
Thanks for your feedback - If you see errors like this you can always submit a PR yourself back to the maintainers to fix it simply by editing the file (in the first case Readme.md) and when you go to commit the change Bitbucket will for the repo and create a PR for you. No worries,I've done that for these 2. For the last…
-
I'm not sure what you mean by "passing in that variable as a Dockerfile argument" - I'm going to assume you mean how would you be able to use that within your build script: If you go to your repo->settings->Deployments->click on a environment (test)-> you can then add a variable, called, say "ENVIRONMENT" and set the value…
-
No, but there is a workaround for this - you can set an environment variable as per Deployment variables under https://confluence.atlassian.com/bitbucket/variables-in-pipelines-794502608.html and let it have the name of the environment in it -
-
Hi Stephen, could you give us a link to the page you saw this on? Thanks, Matt
-
It looks like you're using the https version of the git url - you need to go into Bitbucket and select "clone" and then select the "ssh" url and use that in your package.json.
-
The way to do this is to register a different incoming webhook that maps to the channel you want to notify - essentially the target channel in encoded in the WEBHOOK_URL itself - see step 3 of the slack docs here: https://api.slack.com/incoming-webhooks
-
You'll have to set up your own EC2 account etc - but then we make the actual deployment easy for you with our new Pipes feature where you can use the https://bitbucket.org/atlassian/aws-code-deploy/src/master/ pipe to deploy the code to EC2 using AWS Code Deploy
-
The path to the ZIP_FILE should be relative to where the checkout of your repository is - in this case I imagine it is in the target directory, so you'd need to specify target/hosticawebapp-0.0.1-SNAPSHOT.jar as the ZIP_FILE value.
-
Hi Priyanka, I'm trying to understand what you need help with. Do you need to move your git repository, or do you need to deploy the code or something you build from your repository to an AWS EC2 instance?
-
I'd start with 'Java (Gradle)' but then modify the pipeline according to the instructions in this community post: https://community.atlassian.com/t5/Bitbucket-questions/How-to-setup-Pipelines-for-an-Android-app/qaq-p/424255 That should get you going - I don't know if you'll have to modify the setup to get Kotlin compiled…
-
Hi Luis, We merge the target branch to the source branch when running pull-requests builds, as per https://confluence.atlassian.com/bitbucket/configure-bitbucket-pipelines-yml-792298910.html#Configurebitbucket-pipelines.yml-ci_pull-requestspull-requests This type of pipeline runs a little differently to other pipelines.…
-
Can you post an outline of your bitbucket-pipelines.yml with the correct indenting, or is this the indenting you have in yours? If it is, it is not correct and would result in your pipeline not triggering. Your YML needs to be indented as per the example…
-
As per https://confluence.atlassian.com/bitbucket/caching-dependencies-895552876.html, the compressed cache has to be under 1GB in size to be cached - you can test this in your step's script by compressing the directory yourself and seeing how big it is. There will be a message in the tear down saying the cache is being…
-
Thanks @Nathan Jangula there is indeed now a solution to this