Igor Stoyanov Atlassian Team

Added config directly: script: - IMAGE_NAME="test/bbci-pipes-test-ecr-${BITBUCKET_BUILD_NUMBER}" - docker build -t ${IMAGE_NAME} . - docker image inspect ${IMAGE_NAME} - pipe: atlassian/aws-ecr-push-image:1.6.0 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY…

@mgarcia hi. So i tested this case and found no issues. You can find my config here . As you can see i have IMAGE_NAME test/bbci-pipes-test-ecr-${BITBUCKET_BUILD_NUMBER} which is equal for my build test/bbci-pipes-test-ecr-186 I successfully pushed image to ECR. The only case when i received your error: INFO:…

@Abu Bakir Uralov hi. You can check this articles for windows runners: blog-windows-runners , set-up-runners-for-windows . Regards, Igor.

@Aditya Ekbote hi. We released a new version of google-app-engine-deploy pipe, which use now cloud sdk image 402.0.0-slim. Regards, Igor

@Shivas Fotedar hi. We released a new version of the email-notify pipe, which supports now default parameters of USERNAME, PASSWORD, FROM, TO, HOST. Regards, Igor

@Aakash Shah hi. Could your share also your pre-execution script? Regards, Igor

@TimCoatesNHS hi. Thanks for your question. Unfortunately, we will not implement stack deletion, but if you need this, you can check implementation which you could use in your pipeline. Regards, Igor

@David Harper hi. We will take a look at your pr, but, please, provide a reason why do you need new version of docker image? Regards, Igor

@Abu Bakir Uralov hi. Look at the example below of how to use anchors: image: name: atlassian/default-image:3test: &test parallel: - step: name: Build and Test image: python:3.7 script: - services: - docker - step: name: Lint the Dockerfile image: hadolint/hadolint:latest-debian script: - hadolint Dockerfilepush: &push…

@Georg Duemlein hi. Pipes supports only public docker images. For OIDC support check this pipe for implementation: aws-ecr-push-image Regards, Igor

Also take a look at this response. Regards, Igor.

@Joan Arbelaez hi. Thanks for your question. Please provide us more details with your pipeline config and response to understand what is going wrong. Also take a look at the description of the BITBUCKET_TAG variable: "The tag of a commit that kicked off the build. This value is only available on tags. Not available for…

@Joel Saltzman hi. Thanks for your question. You could find a lot of examples below: Pipelines guides page Regards, Igor

@[deleted] hi. We released a new version of the azure-aks-deploy:1.1.0 pipe, where we updated azure-cli image to version 2.39.0, kubectl to version v1.25.0 with kustomize v4.5.7. Regards, Igor 

@Benoit Verreault hi. We released a new version of the serverless-deploy:1.2.0 pipe, which include upgrades to nodejs16.x and serverless framework V3 Regards, Igor.

@Davide Siluri hi. We released a new version of the serverless-deploy:1.2.0 pipe, which include upgrades to nodejs16.x and serverless framework V3 Regards, Igor.

@Kelly Farlow hi. We released a new version of the serverless-deploy:1.2.0 pipe, which include upgrades to nodejs16.x and serverless framework V3 Regards, Igor.

@Joshua Downer hi. We released a new version of jenkins pipe which supports now self signed certificates. Please provide feedback to us for pipe usage. Regards, Igor.

@plussier hi. Thanks for your feedback. Try this to cover your case (The way the pipeline is written now, I can't set "${CUSTOM_PIPELINE}" to an empty value.) - pipe: atlassian/trigger-pipeline:5.0.1 variables: ... CUSTOM_PIPELINE_NAME: 'null' This will exactly set CUSTOM_PIPELINE_NAME to an empty value (None in python)…

@Yogesh . Thanks for your question. There is no pipe to cover your case. You can try something like this: Create and use your own docker image with kubectl command Then run in the pipelines configuration yml what commands you need: image: name: <your docker image with kubectl> test: &test step: name: test script: - kubectl…

@jamesferreira hi. Good to know you solved your issue. Additionally to your response i will add link to example of firebase-deploy Regards, Igor

Hi @Davide Siluri . Currently no updates.

@awscarla abanes hi. Thanks for your question. Try to read this article. As i understand you have image in Elastic Container Registry (ECR). Also you have In your Elastic Container Service two clusters Test and Production. You already used your image which is placed in ECR in your Test cluster on ECS via updating the…

@bobby jenrow hi. Thanks for your feedback. Your error is due to whitespace in your filter command. Try this in your pipe variables: script: - pipe: atlassian/rsync-deploy:0.7.1 variables: ... 'EXTRA_ARGS_COUNT': 1, 'EXTRA_ARGS_0': "--filter=P assets/css" or if you have more then one extra arg in example 2 args: script: -…

@Joshua Downer hi. Thanks for your question. We will investigate this and notify you if this feature will be added to pipe. Regards, Igor.

And for your case i think you should do something like this in your pipeline: echo $GCP_KEY_FILE_DEV | base64 -d > ~/.client-secret.json gcloud auth activate-service-account --key-file ~/.client-secret.json

Seems i misunderstood you. I thought problem related to pipe. Did you use this pipe: https://bitbucket.org/atlassian/google-app-engine-deploy/src/master/ ? If not maybe you should try?

So, for tests you sent request from your console with your base64 encoded file and without using pipe and you received ok response? Or you received an error even when trying to connect to Google Cloud App Engine from your console?

@Jens Henrik Hosbond hi.Thanks for your question. Looks like the problem relates to base64 encoding. Try to test your encoded variable to check access to Google Cloud App Engine in console. Examples of how to encode: Linux 1$ base64 -w 0 < my_ssh_keyMac OS X 1$ base64 < my_ssh_key Regards, Igor. 

@ajinkyavm hi. Thanks for your question. Try the examples provided here. Regards, Igor.