Oleksandr Kyrdan Atlassian Team

Hi @ka5itoshka , if you need to copy only files that changed in commit you can use the pipe rsync-deploy. More available pipes you can discover on the Bitbucket Pipes page. Cheers, Alex

Hi @Oleksiy , identity file generated via the UI stored in '/opt/atlassian/pipelines/agent/ssh/id_rsa'. A good explanation was provided by @Graham Gatus for the related question How to use generated SSH-KEY in pipelines? Also, to deploy your project, you can use one of the available pipes SFTP deploy, SCP deploy, Rsync…

Hi @Brett Mathe @Oleg Sigida , you can use the Bitbucket Pipelines Artifacts. Save your logs to the artifact file and in the next step read text from that file. Cheers, Alex

Hi @Steve Perry , if I understand you right, you want to deploy just new changes. In your case, you can use the pipe rsync-deploy. More available pipes you can discover on the Bitbucket Pipes page. Cheers, Alex

Hello @Roopesh , In your case, you can use pipe trigger-pipeline. Just add the following snippet to the script section of your bitbucket-pipelines.yml file: - pipe: atlassian/trigger-pipeline:3.1.0 variables: BITBUCKET_USERNAME: $BITBUCKET_USERNAME BITBUCKET_APP_PASSWORD: $BITBUCKET_APP_PASSWORD REPOSITORY:…

Hello Shubhanshu Chouhan, Thank you for your feedback! For now, pipe aws-lambda-deploy implements update code and create/update alias functionality. It's a good suggestion to have update_function_configuration in the current pipe. Will be added in the nearest future. Feel free to provide us any feedback on your experience…

Hi @cjohnson ! An updated version of the Firebase Deploy pipe with a fix is available for now.

Hi @Shabith Thennakone now you can use new pipe Rsync deploy version with SSH_PORT parameter: script: - pipe: atlassian/rsync-deploy:0.2.0 variables: USER: 'ec2-user' SERVER: '127.0.0.1' REMOTE_PATH: '/var/www/build/' LOCAL_PATH: 'build' DEBUG: 'true' SSH_PORT: '8022' Cheers, Alex

Mercurial's repository specific. Looks like the problem with ignoring Mercurial's repository directory in the build and deploy context. File .gcloudignore in your project's directory can solve that issue. # .gcloudignore content .hg .hgignore Added answer according to your case google-app-engine-deploy…

Hello James, Thank you for your reply. Do you use .dockerignore file? If no, try to add it before docker build to ignore Mercurial's repository directory. # .dockerignore content .hg .hgignore More information about .dockerignore here. If you have any additional questions feel free to ask. Cheers, Alex

Hello Castorident, Thank you for your reply. You should add file .gcloudignore to your project's directory. This file specifies files that are *not* uploaded to Google Cloud Platform using gcloud. It follows the same syntax as .gitignore. # .gcloudignore file's content .hg .hgignore .gcloudignore More information about…

Hello Marcel, Thank you for your reply. You can use $BITBUCKET_CLONE_DIR default variable - the absolute path of the directory that the repository is cloned into within the Docker container. LOCAL_PATH: '${BITBUCKET_CLONE_DIR}' #copy the current directory and all included files LOCAL_PATH: '${BITBUCKET_CLONE_DIR}/' #copy…

Pipe "SCP deploy" preserves modification times, access times, and modes from the original file. Try to check permissions on your local at first. But additionally, you can add to your config "SSH run" pipe with a command that modifies targets permissions on the remote: - pipe: atlassian/ssh-run:0.1.3 variables: SSH_USER:…

Hi Duncan, Thank you for your question. In your case use: LOCAL_PATH: '${BITBUCKET_CLONE_DIR}/*' To deploy only files from your directory to the remote you can provide '/local/path/build/*' with trailing asterisk symbol (*) as a LOCAL_PATH variable.

Hi Jan, Hi Wiegert, you can provide '/local/path/build/*' with trailing asterisks symbol (*) as a LOCAL_PATH variable to deploy only files from your build directory to the remote.