Oleksandr Kyrdan Atlassian Team

Hi @Rob Buijs Thank you for your question! Found this discussion and I'll try to help. 1. The empty '-' in the SFTP command is not an issue, pipe use it as part of -b option: man sftp -b batchfile Batch mode reads a series of commands from an input batchfile instead of stdin. Since it lacks user interaction it should be…

Hi @Kevin Helfer We have added support for BCC field: Example sending to multiple recipients using BCC ("Blind Carbon Copy"): script: - pipe: atlassian/email-notify:0.11.0 variables: USERNAME: 'myemail@example.com' PASSWORD: $PASSWORD FROM: 'myemail@example.com' TO: 'myemail@example.com' BCC: 'example1@example.com,…

Hi @Siddhant Pandey Also, you could follow the official guideline for Deployment Concepts and choose your case, as the best practice, take a look into FastAPI in Containers - Docker Best regard, Oleksandr Kyrdan

Hi @osep_redmine Thank you for your question! To try to solve your issue you could create a file with pre-executions logic inside .install-sls-plugins.sh instead of feed it on-fly with echo command, because it depends on shell that you use in the step. and try to set permissions explicitly - chmod 755…

Hi @[deleted] Thank you for your question! The pipe is maintained by sonarsource team, please follow the link in the Support section of the README.md and suggest to do all needed updates. Best regards, Oleksandr Kyrdan

Hi @Sam Mahr Thank you for your question! According to your case, we suggest you to try PRE_EXECUTION_SCRIPT variable to execute script file with some logic with your SSH_KEY. Please, follow the example how to setup SSH inside a pipe's docker container. Example passing pre-execution hook script file (file should have at…

Hi @Zohar Sajith Thank you for your question! Since you use username and password auth you could try alternative atlassian/ftp-deploy pipe instead: script: - pipe: atlassian/ftp-deploy:0.4.1 variables: USER: my-ftp-user PASSWORD: $FTP_PASSWORD SERVER: 127.0.0.1 REMOTE_PATH: /tmp/my-remote-directory To discover more pipes,…

Hi @Jan Laskowski Thank you for your question! Looks like your image was cached on your local machine. To update the image just delete your local image and a new version will be uploaded. Best regards, Oleksandr Kyrdan

Hi @Bibin V Joseph Thank you for your question! It's a good DevOps practice to follow "build once and deploy many". So, the solution could be: step: script: # build the image - docker build -t $IMAGE_NAME:$IMAGE_VERSION -t $IMAGE_NAME:latest . - docker save --output my-docker-image.tar.gz $IMAGE_NAME services: - docker…

Hi @Steve Annett Thank you for your question! We'll fix it in the future release. Best regards, Oleksandr Kyrdan

Hi @Mariusz Dullak A new version of the pipe with your suggestion is released: script: - pipe: atlassian/trigger-pipeline:5.1.2 variables: BITBUCKET_USERNAME: $BITBUCKET_USERNAME BITBUCKET_APP_PASSWORD: $BITBUCKET_APP_PASSWORD REPOSITORY: 'your-awesome-repo' Thanks for contributing to the community! Best regards, Oleksandr…

Thanks for contributing to the community!

Hi @sumit singh Thank you for your question! Please provide us with bitbucket-pipelines.yml configuration details to help you. Best regards, Oleksandr Kyrdan

yep, base required permissions are `Pipelines:Write` and `Repositories:Read` and depends of your configuration of the permissions on the account, workspace, project, try to add combination of: `account:read` and/or `workspace:read` and/or `project:read`

Hi @Mariusz Dullak Thanks for your contributing to the community! Good catch! We'll investigate the issue and notify you. Additionally, depends of your configuration of the permissions on the account, workspace, project, try to add combination of: `account:read` and/or `workspace:read` and/or `project:read`. Best regards,…

Hi @Jiwon Jeon Thank you for your question! You could try the next solution: script: - ... after-script: - if [[ BITBUCKET_EXIT_CODE -eq 0 ]]; then exit 0; else echo "Step failed"; fi - envsubst < ".pipelines/failed_pipe_payload.json.template" > ".pipelines/slack_payload.json" - pipe: atlassian/slack-notify:2.0.0 ... Best…

Hi @Fernando Muller Thank you for your question! The new version of the pipe is released 0.7.0: script: - pipe: atlassian/aws-cloudfront-invalidate:0.7.0 variables: DISTRIBUTION_ID: '123xyz' with the next changes: * Bump version of the base Docker image to python:3.10-slim. * Bump version of boto3 to version 1.26.* and…

Hi @Mikael Landau Thank you for your question! In the example you provided, - docker build -t open-api . - pipe: atlassian/aws-ecr-push-image:2.0.0 variables: IMAGE_NAME: open-api DEBUG: 'true' TAGS: ${BITBUCKET_COMMIT:0:7}-$(date +"%d%m%Y-%H%M%S") make sure you tag docker image with the tag…

Hi @Arman Koradia Thank you for your question! We'll investigate the issue and notify you. Please, pay attention that IMAGE_NAME variable for the pipe should be IMAGE_NAME that you build according to the documentation in the readme. (i.e. "tn-springboot-bitbucket-demo" according to the logs you provided) Also, have you…

Hi @Depstan Thankachan Xavier Thank you for your question! Looks like your ATTACHMENTS file are not correct/or not exist when your build failed. Could you validate and check the testResult with `ls` or `cat` command. Best regards, Oleksandr Kyrdan

@AZZ 1. You could provide the FOLDER variable for the pipe to specify path on you S3 bucket according to the Readme documentation. FOLDER If the deployable artifact is in any folder inside bucket, specify the folder name 2. You should choose only one of the option or upload or deploy at once.

Hi @zoltan_zvara Could you move trigger-pipeline pipe to the separate step? And provide us with logs output because current logs without any errors : - pipe: atlassian/trigger-pipeline:5.0.1 variables: BITBUCKET_USERNAME: $BITBUCKET_USERNAME BITBUCKET_APP_PASSWORD: $BITBUCKET_APP_PASSWORD REPOSITORY: 'repository-name'…

Hi @AZZ Thank you for your question! 1) there is an example in the Readme for your case: script: - pipe: atlassian/aws-code-deploy:1.1.1 variables: AWS_DEFAULT_REGION: 'ap-southeast-2' AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY COMMAND: 'deploy' APPLICATION_NAME:…

Hi @alextcranglesim Thank you for your question! Have you tried these tips? Best regards, Oleksandr Kyrdan

Make sure you encode your SSH_KEY accordingly: Linux base64 -w 0 < my_ssh_key Mac OS X base64 < my_ssh_key and copy/paste the value without trailing symbols. To validate base64 encoded SSH_KEY, try to decode it and use for the direct connection on your local machine.

Hi For this case you need to pass SSH_KEY directly to the pipe SSH_KEYAn alternate SSH_KEY to use instead of the key configured in the Bitbucket Pipelines admin screens (which is used by default). This should be encoded as per the instructions given in the docs for using multiple ssh keys script: - pipe:…

Hi @Brandon Robinson The new version of the aws-ecs-deploy pipe is released: atlassian/aws-ecs-deploy:1.7.0 The boto3 dependency is updated to the latest version (1.26). Best regards, Oleksandr Kyrdan

Hi @redacted The new version of the pipe with details about app password permissions is released atlassian/bitbucket-build-statistics:1.1.1 Best regards, Oleksandr Kyrdan

Hi @Giulio Loffreda Thank you for your question! Have you tried add DEBUG variable to see more debug logs? Best regards, Oleksandr Kyrdan

Hi @Narendra Thank you for your question! If I understand you correct, there could be the next cases: 1) implement your workflow logic in multiple files and combine them with the pipe accordingly: - step: oidc: true script: # <do some pre-build logic> # build the image - docker build -t my-docker-image . # <do some…