Igor Stoyanov Atlassian Team

@Javier Martín we will perform update and notify you when new version will become available. Regards, Igor

Also in the the pipe we use firebase-tools@10.* , could we swap your local firebase CLI to that version to see if you have the same error?

I am not very familiar in firebase but could you check this articles to confirm your case is not one of these: * https://stackoverflow.com/questions/62293474/firebase-doesnt-deploy-new-function-because-it-cant-delete-old-function-cant *…

.

@Oleksandr Sorochynskyi hi. Thanks for your question. You may try to investigate our pipe slack-notify with providing custom constructed payload. Or as an idea you could store your arifacts on s3 using aws-s3-deploy pipe, and then include link to that artifact to the slack-notify message Regards, Igor

Hi @Paul VanRoosendaal . Thanks for your question. Full list of the Azure pipes you can find here. Regards, Igor

@Javier Martín hi. We need more information. Could you share your pipeline configuration and log output for a new and old version of the pipe? Regards, Igor

Hi @Thanapong Yingyong . Thanks for your question. Unfortunately, we don't have any pipe that will deploy to DigitalOcean, but you may try this guide Regards, Igor

@Christopher Hill hi. Thanks for your feedback. It's a good idea to contribute with your custom pull request with your suggested solution for this pipe. Regards, Igor

@Mossroy hi. Thanks for your question. Please, raise a ticket here to gather interests for your feature. Regards, Igor

@Mossroy hi. Thanks for your feedback. We will keep in mind this when we will update this pipe with kubectl 1.26 Regards, Igor

@Marl Bermudo hi. Thanks for your question. Try to use WARMUP_INTERVAL (warmup time for some of customer edgecases) variable. - pipe: atlassian/aws-elasticbeanstalk-deploy:1.0.2 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION…

@Guilherme hi. Thank you for your question. Seems like you are using parallel step so heroku tries to deploy file that not present yet. Remove parallel from the config and all should start work. Regards, Igor

@Yusuf Doctor hi. You can try to use serverless-deploy pipe with preexecution scripts. Example passing preexecution hook script file (file should have at least read and execute permissions): script: - echo 'npm install serverless-additional@2.*' > .my-script.sh - chmod 005 my-script.sh - pipe:…

Hi @Manohar . You can take a look at the azure-web-apps-deploy or azure-web-apps-containers-deploy pipes script: - pipe: atlassian/azure-web-apps-deploy:1.1.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:…

Hi @Taufik Fadlurahman Fajari . It's a good idea to use bitbucket-upload-file pipe. script: - pipe: atlassian/bitbucket-upload-file:0.3.3 variables: BITBUCKET_USERNAME: $BITBUCKET_USERNAME BITBUCKET_APP_PASSWORD: $BITBUCKET_APP_PASSWORD FILENAME: 'app-release.apk' Regards, Igor

Okey, i finally reproduced your issue. I will investigate it and notify you later

Your error was here: git push -u origin main Usually this means you don't have main branch. To ensure that main branch exists i suggested you to manually push to main branch. Also all git commands presented on your provided screenshot. I can't see any problems with your yml configuration, all should work. And yes, if you…

I think, you can, but previously you have to set up some prerequisites. Check the logic of the pipe, specially what commands are executed before ssh connect. Regards, Igor.

yes

@Justin George hi.Thanks for question. Try to use folder parameter according to the docs: script: - pipe: atlassian/npm-publish:0.3.2 variables: NPM_TOKEN: $NPM_TOKEN FOLDER: 'dist' Regards, Igor

Hi @Christof Koegler _Gaims GmbH_ .Thanks for your question. Try manually run all git commands firstly on local machine to see if any errors, then on pipeline without using pipe to see if any errors and notify us with the result. Regards, Igor.

@Frederik Mann hi. Can you confirm that all works on checkstyle-report 0.3.1 but not in version 0.3.2? We bumped violations lib from version 1.116 to 1.149 Regards, Igor.

@oobug hi. Thanks for question. We will update this page. Answering to your question, you can provide or not default variables in pipe.yml, it's up to you. Example with variables: name: My demo pipe ... variables: - name: ENV_NAME default: 'Production' - name: SECRET_KEY default: '${SECRET_KEY}' ... Regards, Igor.

@maole hi. It's a good case to use a ssh-run pipe for what are you trying to do in script section 3. script: - pipe: atlassian/ssh-run:0.4.1 variables: SSH_USER: 'ec2-user' SERVER: '127.0.0.1' COMMAND: 'echo $HOSTNAME' Regards, Igor.

Hi @Abu Bakir Uralov . Thanks for your question. Yes, it's possible, you can check this page for more info about deployments. Regards, Igor.

@Anders Kitson hi. Thanks for your question. Try to use envsubst this way: - envsubst < secure_mongo.json > config.json maybe this will help. Regards, Igor 

@Unni Krishnan hi. Thanks for your question. You should set repository variable AZURE_PASSWORD with value you configured on azure portal. How to setup repository variables Secrets section on azure portal Regards, Igor

@Sarath Nagarajan hi. First of all, please use the latest version of the pipe. We have no clarification of Job ID in our pipe. We use build number of the job, is this what you need to construct your url? Answering to your question, you could create your custom pipe based on jenkins-job-trigger, where you could fetch this…

@David Harper hi. We released a new version of azure-cli pipe, where docker image updated to 2.40.0. Regards, Igor