Igor Stoyanov Atlassian Team

@r.abbasi hi. Do you have warnings in your local build? This was pointed here: https://stackoverflow.com/a/58701621 Regards, Igor.

@ hi. Since you do not use npm in bitbucket-pipeline.yml use image: atlassian/default-image:3 also check and update commands inside your Dockerfile according to https://stackoverflow.com/questions/42308879/how-to-solve-npm-error-npm-err-code-elifecycle

Also similar question: https://community.atlassian.com/t5/Bitbucket-questions/Pipe-error-when-build-test/qaq-p/1099191

@r.abbasi hi. Try to look here https://stackoverflow.com/questions/42308879/how-to-solve-npm-error-npm-err-code-elifecycle

@dataking hi. Yes, you need to create 2 separate cloudformation templates.

@Gaurang Shah hi. I didn't correctly provide you feedback. I thought that the pipe does not support this feature, but seems like it does. We will investigate this feature and provide the feedback later. Regards, Igor.

@Billy Vazquez hi. We have the simple example that describes wait parameter: Update the function 'my-lambda-function' in region 'us-east-1' with the function code contained in 'my-function-code.zip' and wait until lambda update is successful. script: - pipe: atlassian/aws-lambda-deploy:1.4.0 variables: AWS_ACCESS_KEY_ID:…

@r.abbasi hi. Thanks for your question. Try to follow Build and push a Docker image guide. Also the suggestion is not to use node:14.1-alpine, because alpine is minimalistic, instead use the image node:14.1 Regards, Igor

@Gaurang Shah hi. Thanks for your suggestion. It's a good idea to create feature request here: list of requested features Regards, Igor.

@Jake Sheets hi. Thanks for your suggestion. It's a good idea to create feature request here: list of requested features Regards, Igor

@Shivas Fotedar hi. Thanks for your question. Currently this is not possible. We investigate your suggestion and notify you. Regards, Igor

@Ricardo hi. Thanks for your question. Currently our team are working on supporting the default ssh_key for self hosted runner. Please, for now use your custom created ssh key. See how to generate encoded ssh_key under the section: Use multiple SSH keys in your pipeline pass the output in base64 format into bitbucket…

@Billy Vazquez hi. We released new pipe version atlassian/aws-lambda-deploy:1.4.0 to fix this issue. Regards, Igor.

@Thomas Kiesl hi. Thanks for your question. Good example of using sftp-deploy but you need specify which files you want to upload: - pipe: atlassian/ftp-deploy:0.3.6 variables: USER: $USER SERVER: $SERVER PASSWORD: $PASSWORD REMOTE_PATH: $REMOTE_PATH<br><span> LOCAL_PATH</span><span>:</span> <span>build</span> Maybe this…

@Sushant Gudalkar hi. Thanks for your question. You could look at this php deploy template, but replace last step ` atlassian/google-app-engine-deploy:1.0.0` with any of rsync-deploy, ftp-deploy, sftp-deploy.To discover these pipes and other visit our Bitbucket Pipes Marketplace.Regards, Igor

@midasTouchParas hi. Thanks for your question. Maybe you should use node docker image instead of installing manually? Regards, Igor.

@Denis Kisina Hi. We will investigate this issue and notify you about the results. Regards, Igor

@Billy Vazquez hi. Thanks for your investigation. We will fix this in near future. Regards, Igor.

@kamilkloc thanks. I updated the link in my reply

@kamilkloc hi. It's a good idea to create feature request: list of requested features Regards, Igor

@kamilkloc hi. Thanks for your question. Looks like the problem is on your side if it works on the start and after some time it doesn't. Maybe you should check i.e firewall settings or networking etc. Regards, Igor.

@Kalpana Seelam hi. Have you tried this one? https://support.atlassian.com/bitbucket-cloud/docs/deploy-to-kubernetes/ Regards, Igor

@dataking hi. Thanks for your question. Try this to split logic: step: script: - pipe: atlassin/cloudformation-deploy:0.12.0 <create s3 bucket from template> - pipe: atlassian/aws-s3-deploy:1.1.0 <deploy to s3> - pipe: atlassin/cloudformation-deploy:0.12.0 <create lambda> Regards, Igor

@sergio_alba hi. We released new version of aws-lambda-deploy pipe with implemented waiter. Now you could do lambda update configuration and update code with the custom WAIT_INTERVAL: script: - pipe: atlassian/aws-lambda-deploy:1.3.0 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY:…

@Elgiz Abbasov hi. Maybe its good idea: * to create your own docker image with all needed dependencies * or to find in docker hub image that already has most of needed dependencies that you need Regards, Igor

Also i found that self hosted runner does not work with default ssh_key. You should use your custom ssh key. See how to generate encoded ssh_key under the section Use multiple SSH keys in your pipeline of https://support.atlassian.com/bitbucket-cloud/docs/variables-and-secrets/ pass the output in the bitbucket repository…

@max_henash Hi. We released new version of firebase-deploy pipe where firebase-tools bumped to 9.* (latest minor). Regards, Igor.

@Andrés Soria Hi. Currently working on your issue. First what i found is that know_hosts is under /opt/atlassian/pipelines/agent/ssh/known_hosts and since that you don't have this file in your infrastructure (because you didn't update the known hosts from the UI) you have the error: "No SSH known_hosts configured in…

@Elgiz Abbasov Hi. Please provide us your Dockerfile so we could help you. Regards, Igor.

@Elgiz Abbasov Hi. Happy that you solved your issue. To discover more pipes, visit our Bitbucket Pipes Marketplace. Regards, Igor.