Oleksandr Kyrdan Atlassian Team

Hi @Tarek Abdel Sater Thank you for your question! Good suggestion, we'll investigate this feature for the aws-ecr-push-image pipe and notify you. Cheers, Oleksandr Kyrdan

Hi @robtown Thank you for your question! According to the rsync docs you could use one of parameters "--ignore-times", "--ignore-size" or "--checksum" related to your case as an EXTRA_ARGS option for the rsync-deploy pipe: script: - pipe: atlassian/rsync-deploy:0.4.4 variables: USER: 'ec2-user' SERVER: '127.0.0.1'…

Hi @Vitor Oliveira Thank you for your question! We are working on serverless-deploy pipe upgrade. And notify you about upgraded version soon! Cheers, Oleksandr Kyrdan

Hi @Shahidain Thank you for your question! According to the lftp docs, recommended way to use the parameter "--only-newer " or "-n": script: - pipe: atlassian/ftp-deploy:0.3.6 variables: USER: my-ftp-user PASSWORD: $FTP_PASSWORD SERVER: 127.0.0.1 REMOTE_PATH: /tmp/my-remote-directory LOCAL_PATH: build EXTRA_ARGS:…

Hi @t1279k , Thank you for your question! Current version of the aws-ecs-deploy pipe supports update service with a task_definition or force_new_deployment options. To help you, provide us with more details about your case, please. Cheers, Oleksandr Kyrdan

Hi @guilherme_silva , Thank you for your question! Please, provide KUBECTL_ARGS as a YAML list, not as a string: - pipe: atlassian/kubectl-run:1.3.3 variables: KUBE_CONFIG: $KUBE_CONFIG_PRD KUBECTL_COMMAND: 'apply' RESOURCE_PATH: 'deploy/WebApi/Deployment.yml' KUBECTL_ARGS: - "--namespace ${ENVIRONMENT}" We'll investigate…

Hi @marklaff , Thank you for your question! It's a good case for Set up or run parallel steps : pipelines: default: parallel: - step: script: - pipe: atlassian/trigger-pipeline:4.2.1 variables: BITBUCKET_USERNAME: "${FOO_PIPELINE_USER}" BITBUCKET_APP_PASSWORD: "${FOO_PIPELINE_PASS}" BRANCH_NAME: "$BITBUCKET_BRANCH" WAIT:…

Hi @gmlewis , Thank you for your question! Please, provide KUBECTL_ARGS as a YAML list, not as a string: - step: name: Delete any previously-existing rolling-update jobs - OK to fail script: - pipe: atlassian/kubectl-run:1.3.3 variables: KUBE_CONFIG: $KUBE_CONFIG KUBECTL_COMMAND: "delete" KUBECTL_ARGS: -…

Hi @Pimprikar_ Siddharth , Thank you for your question! It's a good case for the email-notify pipe: pipelines: default: - step: name: Build and Test script: - some_build_logic_that_generate__build_zip_artifact artifacts: - build.zip - step: name: Send email script: - pipe: atlassian/email-notify:0.4.3 variables: USERNAME:…

Also, we have open-sourced email-notify pipe, so you could see how it build or use it just adding the next configuration to your pipeline: scripts: - pipe: atlassian/email-notify:0.4.3 variables: USERNAME: 'myemail@example.com' PASSWORD: $PASSWORD FROM: 'myemail@example.com' TO: 'example@example.com' HOST: 'smtp.gmail.com'…

Hi @Jani Ruohomaa Thank you for your question! It's a great case for the custom pipe. We have cool and simple guides How to create a custom pipe as part of 12 days of CI/CD series. Usage example for your custom pipe could be the next: pipelines: default: - step: script: - pipe:…

Hi @Anthony Tsoi , Thank you for your question! We'll investigate this case and notify you. Best regards, Oleksandr Kyrdan

@Brad Vrabete Yep, good question! It shouldn't filter or modify passed params. We are investigating this case and notify you. Thank you! Oleksandr Kyrdan

Hi @Brad Vrabete , Thank you for your question! The pipe atlassian/aws-eks-kubectl-run:1.4.1 based on kubectl v1.17. According to the kubectl v1.17 documentation apply command supports the next flags only: If true, only print the object that would be sent, without sending it. Warning: --dry-run cannot accurately output the…

Hi @NitinKhandelwal , Thank you for your question! Let's simplify the code with an additional variable BUILD_STATUS: after-script: - echo $BITBUCKET_EXIT_CODE - BUILD_STATUS="successful" - if [[ $BITBUCKET_EXIT_CODE -ne 0 ]]; then BUILD_STATUS="failed" ; fi - echo "Step ${BUILD_STATUS}" - pipe: atlassian/email-notify:0.4.3…

Hi @Clayo84 , Thank you for your question! We'll investigate this case and notify you. Best regards, Oleksandr Kyrdan

Hi @aeris_alex , Thank you for your question! We'll investigate this case and notify you. Best regards, Oleksandr Kyrdan

Hi @Natan @c_lingle @Patrick Hynes @judezhu Apologies for the late reply and thanks a lot for your feedback. For some reason, this question was not tagged with the tag "pipes", so we missed it. We fixed this issue and released a new version of the kubectl-run pipe script: - pipe: atlassian/kubectl-run:1.3.3 variables:…

Hi @jposuna , We've released a new version of firebase-deploy pipe. Now it supports NodeJS v14 and has updated firebase-tools v9.4.0. script: - pipe: atlassian/firebase-deploy:1.0.0 variables: KEY_FILE: $KEY_FILE PROJECT_ID: 'myAwesomeProject' MESSAGE: 'Deploying myAwesomeProject' EXTRA_ARGS: '--only functions' It would be…

Hi @Saurabh Singh @Brad Vrabete Thank you for your question! Yep, there was a bug in the pipe with LABELS array and now it is fixed. A new version of the aws-eks-kubectl-run pipe released: script: - pipe: atlassian/aws-eks-kubectl-run:1.4.1 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY:…

Hi @ragnar.callan , Thank you for your question! You could follow a Build Once Deploy Many approach and implement the next pipeline: script: # do other - ... - ... # build the image - docker-compose build # use the pipe to push the image_1 to AWS ECR - pipe: atlassian/aws-ecr-push-image:1.2.2 variables: AWS_ACCESS_KEY_ID:…

Hi @Alexander.ferreras , Thank you for your question! It would be nice if you could provide us with more details about your case to help you: bitbucket-pipelines.yml configuration and brief case description, what are you trying to do? Cheers, Oleksandr

Hi @Joshua Nordstrom , we have released the new version of the atlassian/aws-ecs-deploy:1.4.0 pipe with the TASK_DEFINITION variable optional. In the Advanced examples of the README, you could find details: If your updated Docker image uses the same tag as what is in the existing task definition for your service (for…

Hi @Rahul Johny , Thank you for your question! IMPORTANT! Please, try to avoid post debugged output with your sensitive data. We're highly recommend to change your service password as soon as possible. Is provided port 2232 accessible?

Hi @jposuna , Thank you for your request! We'll investigate a support for NodeJS 14 and notify you. Cheers, Oleksandr

Hi @ilya.pakhomov1010 , Thank you for your question! We've checked pipe's image bitbucketpipelines/rsync-deploy:0.4.4@sha256:ac35ec28011c10616f9744d133614c1df97412bfd6bb731fe68a2c912cc6a7e4 and it's works with rsync inside. We are investigating the issue with the Bitbucket Pipelines team. It would be nice if you could…

Hi @Lara Dias Vasconcelos , Thank you for your question! After build step your pipeline should create build artifacts, so the next step could use them to deploy to AWS S3 bucket. You could use and extend this pipeline: image: node:10.15.3 # Workflow Configuration pipelines: default: - step: name: Build and Test caches: -…

Hi @luberechavarria , Thank you for your question! Yes, we have the guide Deploy to Firebase and the example repository with ready to use pipelines. It would be great if you provide us with feedback about the guide and the pipe. Cheers, Oleksandr

Hi @Anuj , Thank you for your question. It looks like it's AWS issue relates to the latest AWS API update. We're investigating the issue and will notify you of any updates. It would be nice if you provide us with more details: how long have you used aws-esd-deploy pipe with "registeredAt" and "registeredBy" params?

Hi @VR , Thank you for your question! It's a good case to use our ready-to-go template. And don't forget setup your nuget source before according to the dotnet nuget add source guide. dotnet nuget add source https://azureartifacts.microsoft.com/myTeam -n myTeam