Oleksandr Kyrdan Atlassian Team

Hi @Esteban Sanchez Officially released pipes are on Bitbucket Pipes Marketplace. So, please, use atlassian/azure-cli-run pipe instead. It was forked from https://bitbucket.org/microsoft/azure-cli-run for future maintenance purposes. script: - pipe: atlassian/azure-cli-run:1.1.0 variables: AZURE_APP_ID: $AZURE_APP_ID…

To discover more pipes, visit our Bitbucket Pipes Marketplace.

Hi @Esteban Sanchez Thank you for your question! For Azure cloud we have a general-purpose azure-cli-run pipe based on the azure cli: script: - pipe: atlassian/azure-cli-run:1.1.0 variables: AZURE_APP_ID: $AZURE_APP_ID AZURE_PASSWORD: $AZURE_PASSWORD AZURE_TENANT_ID: $AZURE_TENANT_ID CLI_COMMAND: 'az account show' Or it…

Hi @[deleted] Thanks for contributing to the community! Your PR is merged and a new version of git-secrets-scan pipe is released: script: - pipe: atlassian/git-secrets-scan:1.1.0 variables: FILES: '*.txt *.json' Best regards, Oleksandr Kyrdan

Hi @jaya_prakash_ Thank you for your question! It's a good case for azure-storage-deploy pipe: script: - pipe: atlassian/azure-storage-deploy:1.0.2 variables: SOURCE: 'myfile' DESTINATION: 'https://mystorageaccount.blob.core.windows.net/mycontainer/myfile' DESTINATION_SAS_TOKEN: $AZURE_STORAGE_SAS_TOKEN To discover more…

Hi @Asaf Moalem Yes, you are right, this variable is not described in the docs. We'll add it to the Readme soon. Also, code of the pipe is public. If you have any improvements and ideas how to make the pipe better, your PRs are welcome. 👍 Thank your for your contribution to the community! Best regards, Oleksandr Kyrdan

Hi @Asaf Moalem Thank you for your question! More detail for the azure-aks-helm-deploy pipe you could find in the pipe's repository. script: - pipe: atlassian/azure-aks-helm-deploy:2.0.0 variables: AZURE_APP_ID: '<string>' AZURE_PASSWORD: '<string>' AZURE_TENANT_ID: '<string>' AZURE_AKS_NAME: '<string>'…

Hi @[deleted] Thank you for your question! We'll investigate your suggestion with a team and notify you. Best regards, Oleksandr Kyrdan

Hi @tamil.needi Thank you for your suggestion! Currently the jira-create-issue pipe supports only text summary and description. If you’d like to suggest a pipe to be improved or new pipe to be implemented, please, find the appropriate ticket in the list of existing tickets , vote for them or create a new suggestion request…

Hi @Ngeh N @Fabio Racobaldo _Catworkx_ Thank you for your question! Also good idea to follow the 12 Days of CI/CD series and to discover more Bitbucket Pipes as part of Bitbucket Pipelines infrastructure, visit Bitbucket Pipes Marketplace. Best regards, Oleksandr Kyrdan

Hi @Christof Koegler _Gaims GmbH_ We have investigated the issue and found that it could happened when you have a setup with parameters for a branch different than build based on the branch build runs. Documentation is updated accordingly. So, we don't recommend to provide a BITBUCKET_BRANCH variable for the pipe. It will…

Hi @amrsalah944 Thank you for your question! Looks like you try to use outdated (0.2.5) pipe's version with a new (1.1.1) parameters: Currently the latest pipe's version is 1.1.1: script: - pipe: atlassian/aws-code-deploy:1.1.1 variables: COMMAND: 'upload' APPLICATION_NAME: 'my-application' ZIP_FILE: 'myapp.zip' Support…

Hi @amrsalah944 Thank you for your question! It would be nice if you provide us your bitbucket-pipelines configuration to investigate the issue you reported. Best regards, Oleksandr Kyrdan

Hi @Gabriel Moraes Pacheco de Oliveira Thank your for your question! For the integration Bitbucket Pipelines provides Bitbucket Pipes. So you could build powerful, automated continuous integration and continuous deployment workflows in a plug and play fashion. 12 days of CI/CD blog posts series explain and provide details…

Hi @Umagayathri Vasu Thank you for your question! It's a good case for atlassian/aws-ecr-push-image pipe: - step: oidc: true script: # build the image - docker build -t my-docker-image . # use the pipe to push the image to AWS ECR - pipe: atlassian/aws-ecr-push-image:1.5.0 variables: AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION…

@Marco Tanaka Thanks for knowledge sharing and contributing to the community!

Hi @Marco Tanaka Thank you for your question! Make sure that you setup properly OIDC access on AWS according to the Deploy on AWS using Bitbucket Pipelines OpenID Connect guide. Best regards, Oleksandr

@Sander de Kroon Thank you for sharing your solution and contributing to the community.

Hi @Eoghan Dinan Thank you for your question! It's a good case to use pipe in the Bitbucket Pipelines, examples provided in the community answer. Also, please, follow our good Deploy to AWS with Elastic Beanstalk guide. Best regards, Oleksandr Kyrdan

Hi @Aravind Kundurthi Thank you for your question! As an example, you could follow this answer that provides code structure for your bitbucket-pipelines.yaml and an app for the AWS. Also, good example in the repository for the heroku-deploy pipe. Where you deploy your app to the Heroku: script: - pipe:…

Hi @tcuster Thank you for your question! It's a good case to create your own custom pipe. We provide an opensourced tools - Bitbucket Pipes toolkit and good guides for it. To discover more ready to use pipes, visit our Bitbucket Pipes Marketplace. Best regards, Oleksandr Kyrdan

Hi @srikanth Thank you for your question! It's a good case to use Bitbucket Pipes. Use <a href="https://bitbucket.org/atlassian/aws-s3-deploy" target="_blank" rel="noopener noreferrer">aws-s3-deploy</a> pipe to deploy files to S3. Add pipe to your bitbucket-pipelines.yaml configuration: <span style="border: 0px; margin:…

Hi @Sander de Kroon Thank you for your question! Have you tried to move custom docker image usage to the step and add service: - docker parameter? image: name: atlassian/default-image:3 pipelines: default: - step: image: sudwestfryslan/default-pipeline script: - php --version - npm --version service: - docker Also, try to…

Hi @Sven @Noman Ahmed Have your tried to tune WAIT_INTERVAL ? By default, it's setup for 15 sec x 120 attempts = 30 min. WAIT_INTERVAL: Time to wait between polling for deployment to complete (in seconds). Default: 15. The aws-code-deploy pipe supports WAIT_INTERVAL and you could tune it according to your case. To increase…

Hi @Daniel Sartorio , Thank you for your question! The email-notify pipe doesn't have any limits for the number of recipients. Have you try with comma-separated list: example.1@email.com, example.2@email.com Also, it would be nice if you provide us with more details about your pipelines configuration. Best regards,…

Hi @sergio_alba , Good news we have released updated version of the aws-lambda-deploy pipe: * boto3 bumped to the latest 1.18.* version script: - pipe: atlassian/aws-lambda-deploy:1.2.0 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION…

Hi @sergio_alba Thank you for your question! We'll investigate the issue and notify you. Best regards, Oleksandr Kyrdan

Hi @Chris Young Thank you for your feature request! Good suggestion we're working on it and notify you soon. Cheers, Oleksandr Kyrdan

Hi @Monica Gordillo Thank you for your question! Please describe your case. We'll investigate it case and notify you. It'd be nice if you provide us with more details about your pipelines configuration and logs. Best regards, Oleksandr Kyrdan

Hi @Monica Gordillo Thank you for your question! We'll investigate this case and notify you. It'd be nice if you provide us with more details about your pipelines configuration and logs. Best regards, Oleksandr Kyrdan