You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/deployment-environments/tutorial-deploy-environments-in-cicd-azure-devops.md
+17-4Lines changed: 17 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.date: 02/26/2024
12
12
13
13
# Tutorial: Deploy environments in CI/CD by using Azure Pipelines
14
14
15
-
In this tutorial, you will learn how to integrate Azure Deployment Environments (ADE) into your Azure Pipelines CI/CD pipeline.
15
+
In this tutorial, you learn how to integrate Azure Deployment Environments (ADE) into your Azure Pipelines CI/CD pipeline.
16
16
17
17
Continuous integration and continuous delivery (CI/CD) is a software development approach that helps teams to automate the process of building, testing, and deploying software changes. CI/CD enables you to release software changes more frequently and with greater confidence.
18
18
@@ -111,7 +111,7 @@ In Azure Pipelines, you create a *service connection* in your Azure DevOps proje
111
111
1. In the Azure portal, copy the **Display name** value.
112
112
You use this value in the next step to grant permissions for running load tests to the service principal.
113
113
114
-
### Grant access to an ADE project
114
+
### Grant the service connection access to the ADE project
115
115
116
116
Azure Deployment Environments uses role-based access control to grant permissions for performing specific activities on your ADE resource. To make changes from a CI/CD pipeline, you grant the Deployment Environments User role to the service principal.
117
117
@@ -124,6 +124,18 @@ Azure Deployment Environments uses role-based access control to grant permission
124
124
125
125
You can now use the service connection in your Azure Pipelines workflow definition to access your ADE environments.
126
126
127
+
### Grant your account access to the ADE project
128
+
129
+
To view environments created by other users, including the service connection, you need to grant your account read access to the ADE project.
130
+
131
+
1. In the [Azure portal](https://portal.azure.com/), go to your ADE project.
132
+
1. Select **Access control (IAM)** > **Add** > **Add role assignment**.
133
+
1. In the **Role** tab, select **Deployment Environments Reader** in the list of job function roles.
134
+
1. In the **Members** tab, select **Select members**, and then search for your own account.
135
+
1. Select your account from the list, and then select **Select**.
136
+
1. In the **Review + assign tab**, select **Review + assign** to add the role assignment.
137
+
138
+
You can now view the environments created by your Azure Pipelines workflow.
127
139
128
140
## Configure a pipeline
129
141
@@ -148,8 +160,9 @@ The Azure CLI is a command-line tool that provides a set of commands for working
148
160
|`<dev-center-name>`| The name of your dev center. |
149
161
|`<project-name>`| The name of your project. |
150
162
|`<catalog-name>`| The name of your catalog. |
151
-
|`<environment-definition-name>`| Do not change. Defines the environment type that is used. |
152
-
|`<environment-name>`| The name of the environment. |
163
+
|`<environment-definition-name>`| Do not change. Defines the environment definition that is used. |
164
+
|`<environment-type>`| The environment type. |
165
+
|`<environment-name>`| Specify a name for your new environment. |
153
166
|`<parameters>`| Do not change. References the json file that defines parameters for the environment. |
0 commit comments