Igor Stoyanov Atlassian Team

@sbiales hi. Please, next time create a new question to describe your problem. Also could you check this is your case? Regards, Igor

Hi @Bruce Wilcox . According to gcloud app deploy Java17 and 21 versions are supported. google-app-engine-deploy pipe based on google/cloud-sdk:473.0.0, where: There is only one alternative in link group java (providing /usr/bin/java): /usr/lib/jvm/java-11-openjdk-amd64/bin/java Regards, Igor

@cleverleads , @Ashwini Soni hi. Today i tried with this command according to REST API, and it worked correctly. curl -s -L --request GET \ --url 'https://api.bitbucket.org/2.0/repositories/${BITBUCKET_REPO_OWNER}/${BITBUCKET_REPO_SLUG}/downloads/test.yaml' \ --header 'Authorization: Bearer my-token' Maybe it will help…

Hi @André Rugere . We released new version 2.1.0 of the pipe, which allows you to upload to custom blob: script: - pipe: atlassian/google-cloud-storage-deploy:2.1.0 variables: KEY_FILE: $KEY_FILE BUCKET: 'my-bucket' SOURCE: 'myFile.txt' BLOB_NAME_PREFIX: 'my-folder/' Regards, Igor

@André Rugere , pipes are open-sourced, you could suggest feature and follow release process: How to contribute . Or you could wait until our team will implement this feature. Regards, Igor 

@André Rugere , This feature is not supported in current implementation of the pipe. We will investigate it and notify you when new pipe version with this feature will become available. Regards, Igor

@George Betts hi. Thanks for your feedback. First please update to the latest version of the pipe. Next i doubt the problem is with environment variables present. I.e this test passed, despite the fact `AWS_ACCESS_KEY_ID` present in the repository (unfortunately you cannot see it.) I guess the problem is the value of…

@André Rugere hi. Try to rename your files to `folderName/fileName` inside your `files/` folder. Additional details: Google Cloud Storage simulated folders . Regards, Igor

@Sam Mahr hi. We have a plan to upgrade serverless-deploy pipe to Serverless 4.* We will notify you when new version will become available. Regards, Igor

@Ankit Mangla Try to authorize with your credentials from your local computer to exclude problems with azure login. Also in the output you could see the generated command: az login --service-principal --username ef742fcb-f880-4958-98f5-260b8ba0f1 --password DQ.8Q~NCDdjosREDAFDEDwVNAA3NK.4uQxFczd --tenant…

@Jay Seletz hi. We released new version 5.7.0 of the pipe, where retry feature was added. Please, provide feedback if that solved your issue. Regards, Igor 

@ANKIT MANGLA hi. This error means you provided wrong credentials to authenticate to azure cloud. Check these variables: AZURE_APP_IDAZURE_PASSWORDAZURE_TENANT_ID Also maybe you have to set an AZURE_SUBSCRIPTION if you use it? Regards, Igor

@sschroders hi. New version azure-storage-deploy:2.4.0 released, which will automatically guess the content-type of files. Please, provide feedback if this version solved your problem. Regards, Igor

@sschroders hi. New version azure-storage-deploy:2.4.0 released, that allows you to copy the content of a directory: script: - pipe: atlassian/azure-storage-deploy:2.4.0 variables: SOURCE: 'my-directory/*' DESTINATION_STORAGE_ACCOUNT_NAME: 'https://mystorageaccount.blob.core.windows.net' DESTINATION_SAS_TOKEN:…

@Mark C - The feature @Jay Seletz asked is still in development. Regards, Igor

@Mark C . It is not an environment variable, it is the default name of Azure Storage Container. Regards, Igor

@Maruf hi. Have you tried this solution: '\$web' according to Escape character Bash Regards, Igor

@sschroders hi. Azure automatically set the default application/octet-stream content type. I will try to provide a solution for this case in future releases. Regards, Igor

@Geoff L. hi. Thanks for your question. If you do not have VERSION variable, you should generate a semversioner file. Check Release process paragraph, example: generate changeset with command semversioner add-change --type patch --description "Fix security vulnerability with authentication." After that you will be able to…

@Lokesh M hi. Thanks for your question ✖ /opt/atlassian/pipelines/agent/build/application.zip directory doesn't exist. This error points you that you should pass a directory not a file. According to aws-s3-deploy README: LOCAL_PATH - Local path to folder to be deployed. Example: script: - pipe:…

@Jay Seletz hi. We will consider to implement your feature request with retry functionality on trigger build. We will notify you when new pipe version will become available. Regards, Igor

duplicate 

I will investigate this, add this as feature request to the pipe, and notify you when this feature will become available. Regards, Igor

With this version of the pipe you may upload only file or a directory, not the content of a directory. Update: you could try to cd to needed directory and then provide a dot as source: - cd dist - pipe: atlassian/azure-storage-deploy:2.2.1 variables: SOURCE: '.' Please, provide a feedback if this helped you. Regards, Igor

@ishetnogferre hi. New version of the pipe with azure subscription available: script: - pipe: atlassian/azure-web-apps-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: 'my-site' ZIP_FILE:…

@Oleksandr Kyrdan 

@Victor Ferreira Hi. Microsoft pipe: https://bitbucket.org/microsoft/azure-storage-deploy/src/master/ is not supported anymore. To deploy a directory with https://bitbucket.org/atlassian/azure-storage-deploy/src/master/ try to provide a directory name without wildcard: script: - pipe: atlassian/azure-storage-deploy:2.2.1…

@ishetnogferre hi. Thanks for your feature request. We will add this feature to the azure-web-apps-deploy pipe and notify you when new pipe release will become available. Regards, Igor

@Knittchen hi. Thank you for your suggestion. Our team will implement changes to this logic and notify you. Regards, Igor

@itsjayalekharamesh hi. It is hard to understand what is going wrong. Try to use serverless deploy cli directly to find the root cause. Regards, Igor.