The following plugin provides functionality available through
Pipeline-compatible steps. Read more about how to integrate steps into your
Pipeline in the
section of the
For a list of other such plugins, see the
Pipeline Steps Reference
Azure App Service Plugin
azureWebAppPublish: Publish an Azure Web App
The Azure Service Principal credentials used to communicate with the Azure services. Check the following documentation for more information about the service principal:
The resource group name that the app will be associated with.
If checked, the intermediate docker image will be removed from your build agent after build succeeds.
If checked, application will only be deployed to Azure if the build was successful.
The docker image name. Leave blank if you want to use the same name as it on Azure.
Be sure to include the registry and account if any. See examples:
Docker hub format: <username>/<name> eg. bitname/mysql
Azure registry format: <namePrefix.azurecr.io>/<repo> eg. xxx.azurecr.io/mysql, xxx.azurecr.io/yyy/mysql
Tha tag for your image. It's recommended to use a different tag for every single build otherwise your previous images might be overridden. We suggest you to append the BuildNumber to your tag so you can easily know that with which image your web app is currently running.
URL to the Docker registry you are using. May be left blank to use the public DockerHub registry (currently
The file paths that will be deployed.
You can use wildcards like
module/dist/**/*.py. See the includes attribute of Ant fileset for the exact format. Multiple files can be separated by '
,'. The base directory is the workspace. You can only deploy files that are located in your workspace.
Note: For Java application, usually you should put your war file under the 'webapps' directory.
If not blank, will deploy to this deployment slot instead of the default production slot.
See this article for more details.
Source directory relative to the workspace.
Target directory relative to the site root.
Was this page helpful?
Please submit your feedback about this page through this
Alternatively, if you don't wish to complete the quick form, you can simply
indicate if you found this page helpful?
See existing feedback here.