Skip to content

Commit 46811ef

Browse files
committed
add a step to show job status
1 parent 9b403b0 commit 46811ef

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/azure-resource-manager/templates/add-template-to-azure-pipelines.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: CI/CD with Azure Pipelines and templates
33
description: Describes how to configure continuous integration in Azure Pipelines by using Azure Resource Manager templates. It shows how to use a PowerShell script, or copy files to a staging location and deploy from there.
44
ms.topic: conceptual
5-
ms.date: 03/09/2021
5+
ms.date: 02/07/2022
66
---
77
# Integrate ARM templates with Azure Pipelines
88

@@ -172,20 +172,20 @@ The following YAML shows the [Azure Resource Manager template deployment task](h
172172

173173
There are several parts of this task to review in greater detail.
174174

175-
- `deploymentScope`: Select the scope of deployment from the options: `Management Group`, `Subscription`, and `Resource Group`. To learn more about the scopes, see [Deployment scopes](deploy-rest.md#deployment-scope).
175+
* `deploymentScope`: Select the scope of deployment from the options: `Management Group`, `Subscription`, and `Resource Group`. To learn more about the scopes, see [Deployment scopes](deploy-rest.md#deployment-scope).
176176

177-
- `azureResourceManagerConnection`: Provide the name of the service connection you created.
177+
* `azureResourceManagerConnection`: Provide the name of the service connection you created.
178178

179-
- `subscriptionId`: Provide the target subscription ID. This property only applies to the Resource Group deployment scope and the subscription deployment scope.
179+
* `subscriptionId`: Provide the target subscription ID. This property only applies to the Resource Group deployment scope and the subscription deployment scope.
180180

181-
- `resourceGroupName` and `location`: provide the name and location of the resource group you want to deploy to. The task creates the resource group if it doesn't exist.
181+
* `resourceGroupName` and `location`: provide the name and location of the resource group you want to deploy to. The task creates the resource group if it doesn't exist.
182182

183183
```yml
184184
resourceGroupName: '<resource-group-name>'
185185
location: '<location>'
186186
```
187187

188-
- `csmFileLink`: Provide the link for the staged template. When setting the value, use variables returned from the file copy task. The following example links to a template named mainTemplate.json. The folder named **templates** is included because that where the file copy task copied the file to. In your pipeline, provide the path to your template and the name of your template.
188+
* `csmFileLink`: Provide the link for the staged template. When setting the value, use variables returned from the file copy task. The following example links to a template named mainTemplate.json. The folder named **templates** is included because that where the file copy task copied the file to. In your pipeline, provide the path to your template and the name of your template.
189189

190190
```yml
191191
csmFileLink: '$(AzureFileCopy.StorageContainerUri)templates/mainTemplate.json$(AzureFileCopy.StorageContainerSasToken)'
@@ -224,7 +224,7 @@ steps:
224224
deploymentName: 'deploy1'
225225
```
226226

227-
When you select **Save**, the build pipeline is automatically run. Go back to the summary for your build pipeline, and watch the status.
227+
When you select **Save**, the build pipeline is automatically run. Under the **Jobs** frame, select **Job** to see the job status.
228228

229229
## Next steps
230230

0 commit comments

Comments
 (0)