Azure App Service

What it does

This action uploads your files from Buddy’s pipeline filesystem to Azure App Service, the Microsoft’s platform as a service (PaaS) environment letting developers easily publish and manage websites.

How it works

The action pushes the repository, including files generated by previous actions and saved to the pipeline’s filesystem, to selected branch in Azure App.

To connect the action with the Azure App Service, go to your web app’s blade and click Overview. There will be a Get publish profile link on the top. Click it to download the XML file with publishing data. Select the Azure action and paste the following values from the downloaded XML file:

• publishURL: publishData//publishProfile//publishUrl
• login: userName with a $ sign
• password: userPWD

Make sure to provide the data from the publish profile with publishMethod="MSDeploy, not publishMethod="FTP".

Learn more how to set up CI/CD with Buddy and Azure

Action preview

SetupConditionAction

Image loading...

Azure App Service Action Features

• By default the action uses .gitignore from the repository, but it’s possible to set custom .gitignore in the action settings. The option could be used to push artifacts that we don’t want to store in the repository
• If Don't deploy changes made by previous actions is set, changes made by other actions in the pipeline filesystem will be ignored (like changed the files or generated artifacts)
• When Without force is selected, this action will fail on conflicts
• App service deployment branch: by default, Buddy pushes your changes to the master branch in the Azure repository from which the deployment is made. Do not change it unless you have changed the deployment branch in Azure’s settings
• The action can be configured in YAML mode. See Azure App Service YAML parameters and Azure App Service YAML config example
• Buddy's Azure App Service API is supported
• The action supports conditional execution: it can be run on each execution, only if there are changes in the repository or specific paths since last execution, or if an environment variable has a specific value
• Handling failures: you can either stop the execution, mark action and pipeline as failed or proceed the execution, mark action as warning and jump to the next action

More about Azure App Service

• How to deploy to Azure App Service
• Set up & manage Azure App Service integration