Oleksandr Kyrdan Atlassian Team

Hi @siddharthjoshi Thank you for your question! Have you provided all parameters required parameters for pipe? Do you have permissions to push images to that repository? It would be nice if you provide us with more details to help you: pipeline configuration, logs, etc. Cheers, Oleksandr Kyrdan

Hi @Sanket Sultan Thanks for contributing and sharing the solution with the community! Best regards, Oleksandr Kyrdan

Hi @mark Thank you for your question! We'll investigate this feature and notify you. Cheers, Oleksandr Kyrdan

How about this one? - ping SERVER_IP

@[deleted] thanks, good suggestion. It's a good practice to rotate generated secrets periodically. As an alternative you could use an OAuth consumer on Bitbucket Cloud. If you’d like to suggest feature to improve, please, find the appropriate ticket in the list of existing tickets, vote for them or create a new suggestion…

@[deleted] Please take a look at trigger pipeline pipe source code under the hood, as it's open sourced ) Here are payload structure and parameters required for programmatically API interaction from the Python code. Note! Remember to check the Pipelines Write and Repositories Read permissions when generating the app…

Hi @Lucas Possamai Thank your for sharing working solution and contributing to the community! Best regards, Oleksandr Kyrdan

Hi @[deleted] Thank you for your question! It's a good case for trigger-pipeline pipe. To use this pipe, you need to generate an app password. Remember to check the Pipelines Write and Repositories Read permissions when generating the app password. If you want to trigger a pipeline in a repository owned by a team account,…

Hi @Nicolas BROUET Thank you for your question! Have you check if it's possible to connect to you server from bitbucket pipelines before using the pipe? Best regards, Oleksandr Kyrdan

Hi @Jeff Taylor Thank you for your suggestion. We'll investigate this case and notify you. Best regards, Oleksandr Kyrdan

Hi @Arun kumar gupta Thank you for your question! Provide us with more details about your errors (logs, setup configuration), please, to help you. Best regards, Oleksandr Kyrdan

Hi @Jason Harrison , Thank you for your question! Could you clarify your case to help you? If you mean to send notification about failed build to slack or email, you could setup after-script: image: atlassian/default-image:2 pipelines: default: - step: name: Build script: - echo "Main logic here... If step failed…

Hi @Caleb Scholze Thank you for your feedback! We are investigating this behaviour and notify you. Best regards, Oleksandr Kyrdan

Hi @davi.carvalho Thank you for your question! We'll investigate this feature and notify you! Cheers, Oleksandr Kyrdan

Hi @Ian Anderson Thank you for your feedback! We'll fix this behaviour and notify you. Best regards, Oleksandr Kyrdan

Hi @Breno The new version with fix released: script: - pipe: atlassian/aws-elasticbeanstalk-deploy:1.0.1 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION: 'us-east-1' APPLICATION_NAME: 'my-app-name' ENVIRONMENT_NAME: 'production' ZIP_FILE: 'application.zip'…

Hi @Martin Cassidy , The new version with fix released: script: - pipe: atlassian/kubectl-run:3.0.1 variables: KUBE_CONFIG: $KUBE_CONFIG KUBECTL_COMMAND: 'apply' RESOURCE_PATH: 'nginx.yml' It would be great if you provide us with your feedback about the pipe. Cheers, Oleksandr Kyrdan

Hi @Pavel Alazankin , Great suggestion! Thank you! Cheers, Oleksandr Kyrdan

Hi @Stuart Smiley Thank you for your question! We're investigating it and notify you. Best regards, Oleksandr Kyrdan

Hi @Châu Nguyễn Trung , Now Flexible payload supported in atlassian/slack-notify:1.2.0: script: - envsubst < "payload.json.template" > "payload.json" - pipe: atlassian/slack-notify:1.2.0 variables: WEBHOOK_URL: $WEBHOOK_URL PAYLOAD_FILE: payload.json Use custom payload created with Slack Block Kit and modify payload with…

Yep, it's better to create the template file in your repository. You don't need destination file anymore. Destination file will be generated automatically on each build.

Note! For future maintenance purposes we have forked the microsoft/azure-aks-deploy pipe from https://bitbucket.org/microsoft/azure-aks-deploy. Now it is available as atlassian/azure-aks-deploy:1.0.2: script: - pipe: atlassian/azure-aks-deploy:1.0.2 variables: AZURE_APP_ID: $AZURE_APP_ID AZURE_PASSWORD: $AZURE_PASSWORD…

Hi @Reethu Thank you for your question! To make image name flexible try envsubst (the program substitutes the values of environment variables) instead: - envsubst < aks-deployment.yaml.template > aks-deployment.yaml Add to your repository template aks-deployment.yaml.template file: containers: - name: containername image:…

Hi @fibrasek Thank you for your question! It's a good case for trigger-pipeline pipe: script: - pipe: atlassian/trigger-pipeline:4.2.1 variables: BITBUCKET_USERNAME: $BITBUCKET_USERNAME BITBUCKET_APP_PASSWORD: $BITBUCKET_APP_PASSWORD REPOSITORY: 'your-awesome-repo' To discover more pipes, visit our Bitbucket Pipes…

Hi @SatoruNakada @Aron Gombas _Midori_ , Also, you could simplify your pipeline with pipes. aws-s3-deploy pipe syncs directories and S3 prefixes. Recursively copies new and updated files from the source local directory to the destination: script: - pipe: atlassian/aws-s3-deploy:1.1.0 variables: S3_BUCKET: 'my-bucket-name'…

Hi @Gabriel Bellon Thank you for your question! It's a good time to update pipe's Readme! We'll update the pipe and notify you. Cheers, Oleksandr Kyrdan

Hi @Noman Ahmed Thank you for your question! We are investigating this issue and notify you. Cheers, Oleksandr Kyrdan

Hi @Martin Cassidy Thank you for your question! We'll investigate this issue and notify you. Cheers, Oleksandr Kyrdan

Hi @Leonardo Medici Some summary after the issue investigation, Started from version 1.0.0 aws-s3-deploy pipe uses AWS CLI version 2. So, now AWS CLI version 2 more strict for filenames/key-names: only utf-8 supported. So, the official AWS S3 Creating object key names guide should be updated by AWS to the next: Object key…

Looks like this issue relates to the changes in behavior between AWS CLI version 1 and AWS CLI version 2 One of the reason could be locale: AWS CLI version 2 now uses environment variable to set text file encoding By default, text files use the same encoding as the installed locale. To set encoding for text files to be…