Igor Stoyanov Atlassian Team

@Dimitry Kudryavtsev hi. According to pipe README: Prerequisites To use this pipe you should have a IAM user configured with programmatic access or Web Identity Provider (OIDC) role, with the necessary permissions to push docker images to your ECR repository. You also need to set up an ECR container registry if you don't…

We created a new release of aws-ecr-push-image according to this feature request. Now users have to build and tag all images they want to push with requested tags: script: # build the image - docker build -t my-docker-image:my-tag -t my-docker-image . # use the pipe to push to AWS ECR - pipe:…

@Gilbert Bencito i don't know exactly, but check this page. Regards, Igor

@Gilbert Bencito hi. Thanks for your question. Try this example if you want to clear your s3 bucket before upload. script: - pipe: atlassian/aws-s3-deploy:1.1.0 variables: S3_BUCKET: 'my-bucket-name' LOCAL_PATH: 'build' EXTRA_ARGS: "--delete" Under the hood pipe use `aws sync` command: <span>--delete</span> (boolean) Files…

@Brandon Robinson hi. Thanks for your question. Looks like boto3 library should be updated in this pipe to fix this error (add support for it): <span>✖ ECS task definition parameter validation error: </span><span>Parameter validation failed:</span><span>Unknown parameter in containerDefinitions[0].portMappings[0]: "name",…

@Marcos Almeida hi. "How can I deploy without creating that folder." Try this example: Copy recursively to the remote server directories and files without source directory build. script: - pipe: atlassian/ftp-deploy:0.4.0 variables: USER: my-ftp-user PASSWORD: $FTP_PASSWORD SERVER: 127.0.0.1 REMOTE_PATH:…

@Joao Clemente our team has this task in JIRA backlog (where you do not have access), scheduled on next sprint, so new version will approximately be available on February 20 if nothing changes. We have an option to create issues to track status, for this issues we collecting votes and then decide if we should include the…

@Joao Clemente hi. Thanks for investigation. Good catch. We will additionally check this and notify you about new version if we decide to implement your suggestion. Regards, Igor

@Dryden Linden-Bremner hi. Currently DigitalOcean is not supported by default because it depends on plugin that not presented in the pipe. We will investigate how to expand the pipe logic with custom plugins and notify you when this feature becomes available. Regards, Igor

@BradyEdgar94 hi. Try this command: yarn install --non-interactive But also i suggest you to take a look at our pipes marketplace. There are some of them to work with the node and maybe they will cover your case. Regards, Igor

Hi @redacted . We released a new pipe version, which allows you to out put results in json format: - pipe: atlassian/bitbucket-build-statistics:1.1.0 variables: BITBUCKET_USERNAME: $BITBUCKET_USERNAME BITBUCKET_APP_PASSWORD: $BITBUCKET_APP_PASSWORD FILENAME: "build_usage.txt" Regards, Igor

Hi, so if I get it right, the pipe will always take the local $IMAGE_NAME with tag="latest" and push that to the specified TAGS on remote? Yes. ^ this would then push the "latest" local tag to all 3 remote $TAGS, which is probably not what one would expect. Yes, this will fail. We will think about adding a note to the pipe…

@[deleted] hi. Thanks for your investigation. According to pipe documentation you have to follow the next: Don't add tag in the IMAGE_NAME variable, pass variables TAGS instead (see more information below). So yes, this pipe relies on latest tag, but if you will follow this configuration: script: # build the image - docker…

@O Devops hi. If i correctly understood you, when pull request declined, then no merge happened, so no pipeline triggered. Regards, Igor

@Nicolas Hunter hi. Thanks for your question. Check this answer, is this your case? Regards, Igor.

@Vladimir Vlach we released a new version, where this feature request implemented: https://bitbucket.org/atlassian/aws-lambda-deploy/src/1.7.0/ Regards, Igor.

@kanchan patil hi. Maybe this article will help you. Regards, Igor

@nagaraju hi. Try this guide and azure-aks-deploy pipe. script: - pipe: atlassian/azure-aks-deploy:1.1.0 variables: AZURE_APP_ID: $AZURE_APP_ID AZURE_PASSWORD: $AZURE_PASSWORD AZURE_TENANT_ID: $AZURE_TENANT_ID AZURE_AKS_NAME: 'my-cluster' AZURE_RESOURCE_GROUP: 'my-resource-group' KUBECTL_COMMAND: 'version' Regards, Igor

@Omkar posam hi. You have to understand where you put your artifact. Under your script check where you are (add some ls command to debug): script: - cd AdminPortal_WebAPI -ls -la - apt-get update && apt-get install -y apt-utils - dotnet build --configuration Release -o AdminPortal_WebAPI/pipelineoutput - cd…

@biyani.11 hi. Try this one: azure-web-apps-containers-deploy script: - pipe: atlassian/azure-web-apps-containers-deploy:1.2.0 variables: AZURE_APP_ID: $AZURE_APP_ID AZURE_PASSWORD: $AZURE_PASSWORD AZURE_TENANT_ID: $AZURE_TENANT_ID AZURE_RESOURCE_GROUP: $AZURE_RESOURCE_GROUP AZURE_APP_NAME: $AZURE_APP_NAME…

@tomcatbuzz : "since before we could simply use a token before <- easy." this method is still available.

@Ronak Toshniwal check in example this: https://bitbucket.org/atlassian/aws-cloudformation-deploy/pull-requests/51 Initial build when pr created was this one: https://bitbucket.org/atlassian/aws-cloudformation-deploy/pipelines/results/334 And when pr was merged next build ran:…

@tomcatbuzz hi. Create a new question and provide more details with your pipeline config and log output. Have you created your KEY_FILE variable according to this article? bitbucket-cloud/docs/use-multiple-ssh-keys-in-your-pipeline Linux base64 -w 0 < your_key_file Mac base64 < your_key_file and then pass the result as…

@Niek Kouwenberg hi. pipe: atlassian/bitbucket-upload-file:latest will not work. You the ability to use latest docker image with: pipe: docker://bitbucketpipelines/bitbucket-upload-file:latest but this is a bad idea. In case of some major pipe changes your pipeline build will stop working. Also in case of some minor pipe…

By default the pipe will use nodeJS version 16. You could change this with i.e to use nodeJS version 18 for hosting with `NODE_JS_VERSION` variable: script: - pipe: atlassian/firebase-deploy:3.1.1 variables: KEY_FILE: $KEY_FILE NODE_JS_VERSION: '18' Supported values are: 14, 16 (default), 18. With `firebase deploy --only…

@Larry Johnson @tomcatbuzz @Danilo Lombardi hi. We released a new version 3.1.1 of the firebase-deploy pipe, where the bug should be fixed. Waiting for your feedback. Regards, Igor

@Asif332 hi. Seems like it's not supported. Check this thread for more details. Regards, Igor.

@Larry Johnson ```It probably is unreasonable to require the pipeline to support multiple node versions. ``` we already support multiple node versions: n@6.7.0 && n 8 && n 10 && n 12 && n 14 && n 16 ``` line 75 always reverses whatever may be done in line 69.``` -- thats true, this will be fixed. I will add a little…

@Larry Johnson hi. Is it possible in monorepo in different function packages.json have different node versions? I think about fetching node version from the first element of the list of functions. Is this correct? Or do you think it is better to just provide node version as a pipe variable NODE_VERSION? This solutions will…

@Felipe Micheletto Try to delete/add_again DISTRIBUTION_ID in the repository variables. Check in the logs this line: ```Distibution URL: https://console.aws.amazon.com/cloudfront/home?region={region}#distribution-settings:{distribution_id}``` -- is this the correct link? If this will not help, try to call cli command…