|
2 | 2 | title: Configure CI/CD with Azure Pipelines
|
3 | 3 | description: Learn how to deploy your code to Azure App Service from a CI/CD pipeline with Azure DevOps Pipelines.
|
4 | 4 | ms.topic: article
|
5 |
| -ms.date: 06/08/2022 |
| 5 | +ms.date: 06/14/2022 |
6 | 6 | ms.author: jukullam
|
7 | 7 | ms.manager: mijacobs
|
8 | 8 | ms.custom: "devops-pipelines-deploy"
|
@@ -33,6 +33,10 @@ You'll use the [Azure Web App task](/azure/devops/pipelines/tasks/deploy/azure-r
|
33 | 33 |
|
34 | 34 | ### Create your pipeline
|
35 | 35 |
|
| 36 | +The code examples in this section assume you are deploying an ASP.NET web app. You can adapt the instructions for other frameworks. |
| 37 | + |
| 38 | +Learn more about [Azure Pipelines ecosystem support](azure/devops/pipelines/ecosystems/ecosystems). |
| 39 | + |
36 | 40 | # [Classic](#tab/yaml/)
|
37 | 41 |
|
38 | 42 | 1. Sign in to your Azure DevOps organization and navigate to your project.
|
@@ -103,16 +107,18 @@ To get started:
|
103 | 107 |
|
104 | 108 | Now you're ready to read through the rest of this topic to learn some of the more common changes that people make to customize an Azure Web App deployment.
|
105 | 109 |
|
106 |
| -## Use the Azure Web App task |
| 110 | +## Use the Azure Web App task (.NET, ) |
107 | 111 |
|
108 | 112 | # [YAML](#tab/yaml/)
|
109 | 113 |
|
110 |
| -The simplest way to deploy to an Azure Web App is to use the **Azure Web App** (`AzureWebApp`) task. |
| 114 | +The Azure Web App Deploy task is the simplest way to deploy to an Azure Web App. By default, your deployment happens to the root application in the Azure Web App. |
| 115 | +
|
| 116 | +The [Azure App Service Deploy task](/azure/devops/pipelines/tasks/deploy/azure-rm-web-app-deployment) allows you to modify configuration settings inside web packages and XML parameters files. |
111 | 117 |
|
112 |
| -### Deploy a Web Deploy package (ASP.NET) |
| 118 | +### Deploy a Web Deploy package |
113 | 119 |
|
114 | 120 | To deploy a .zip Web Deploy package (for example, from an ASP.NET web app) to an Azure Web App,
|
115 |
| -add the following snippet to your azure-pipelines.yml file: |
| 121 | +add the following snippet to your *azure-pipelines.yml* file: |
116 | 122 |
|
117 | 123 | ```yaml
|
118 | 124 | - task: AzureWebApp@1
|
@@ -158,27 +164,6 @@ steps:
|
158 | 164 | * **appName**: the name of your existing app service.
|
159 | 165 | * **package**: the file path to the package or a folder containing your app service contents. Wildcards are supported.
|
160 | 166 |
|
161 |
| -### Deploy a JavaScript Node.js app |
162 |
| - |
163 |
| -If you're building a [JavaScript Node.js app](/azure/devops/pipelines/ecosystems/javascript), you publish the entire contents of your |
164 |
| -working directory to the web app. This snippet also generates a Web.config file during deployment if the application does not have one and starts |
165 |
| -the iisnode handler on the Azure Web App: |
166 |
| - |
167 |
| -```yaml |
168 |
| -- task: AzureWebApp@1 |
169 |
| - inputs: |
170 |
| - azureSubscription: '<Azure service connections>' |
171 |
| - appName: '<Name of web app>' |
172 |
| - package: '$(System.DefaultWorkingDirectory)' |
173 |
| - customWebConfig: '-Handler iisnode -NodeStartFile server.js -appType node' |
174 |
| -``` |
175 |
| - |
176 |
| -* **azureSubscription**: your Azure subscription. |
177 |
| -* **appName**: the name of your existing app service. |
178 |
| -* **package**: the file path to the package or a folder containing your app service contents. Wildcards are supported. |
179 |
| -* **customWebConfig**: generate web.config parameters for Python, Node.js, Go, and Java apps. A standard `web.config` file will be generated and deployed to Azure App Service if the application does not have one. |
180 |
| - |
181 |
| -For information on Azure service connections, see the [following section](#endpoint). |
182 | 167 |
|
183 | 168 | # [Classic](#tab/classic/)
|
184 | 169 |
|
@@ -497,3 +482,4 @@ You're now ready to create a release, which means to run the release pipeline wi
|
497 | 482 |
|
498 | 483 | 1. After the release is complete, navigate to your site running in Azure using the Web App URL `http://{web_app_name}.azurewebsites.net`, and verify its contents.
|
499 | 484 |
|
| 485 | + |
0 commit comments