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
{{ message }}
This repository was archived by the owner on Jan 21, 2026. It is now read-only.
Copy file name to clipboardExpand all lines: Instructions/Labs/AZ400_M03_L04_Configuring_Agent_Pools_and_Understanding_Pipeline_Styles.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ YAML-based pipelines allow you to fully implement CI/CD as code, in which pipeli
24
24
25
25
Regardless of the choice of the pipeline style, to build your code or deploy your solution by using Azure Pipelines, you need an agent. An agent hosts compute resources that run one job at a time. Jobs can be run directly on the host machine of the agent or in a container. You have an option to run your jobs using Microsoft-hosted agents, which are managed for you, or implementing a self-hosted agent that you set up and manage on your own.
26
26
27
-
In this lab, you'll step through converting a classic pipeline into a YAML-based one and running it first by using a Microsoft-hosted agent and then performing the equivalent task using a self-hosted agent.
27
+
In this lab, you will learn how to implement and use self-hosted agents with YAML pipelines.
28
28
29
29
## Objectives
30
30
@@ -132,7 +132,7 @@ In this task, you will configure the LOD VM as an Azure DevOps self-hosting agen
132
132
| Enter agent pool (press enter for default) | **az400m05l05a-pool** |
133
133
| Enter agent name | **az400m05-vm0** |
134
134
| Enter work folder (press enter for _work) | **Enter** |
135
-
| **(Only if shown)** Enter Perform an unzip for tasks for each step. (press enter for N) | **Enter** |
135
+
| **(Only if shown)** Enter Perform an unzip for tasks for each step. (press enter for N) | **WARNING**: only press **Enter** if the message is shown|
136
136
| Enter run agent as service? (Y/N) (press enter for N) | **Y** |
137
137
| enter enable SERVICE_SID_TYPE_UNRESTRICTED (Y/N) (press enter for N) | **Y** |
138
138
| Enter User account to use for the service (press enter for NT AUTHORITY\NETWORK SERVICE) | **Enter** |
@@ -153,6 +153,9 @@ In this task, you will configure the LOD VM as an Azure DevOps self-hosting agen
153
153
demands:
154
154
- agent.name -equals az400m05-vm0
155
155
```
156
+
> **WARNING**: Be careful with copy/paste, make sure you have same indentation shown above.
157
+
158
+
156
159
1. For `Task: NugetToolInstaller@0`, click on **Settings (link that is displaying above the task in grey colour)**, modify **Version of NuGet.exe to install** > **4.0.0** and click on **Add**.
157
160
1. On the **PartsUnlimited** edit pane, in the upper right corner of the pane, click **Save** and, on the **Save** pane, click **Save** again. This will automatically trigger the build based on this pipeline.
158
161
1. In the Azure DevOps portal, in the vertical navigational pane on the left side, in the **Pipelines** section, click **Pipelines**.
@@ -162,4 +165,4 @@ In this task, you will configure the LOD VM as an Azure DevOps self-hosting agen
162
165
163
166
## Review
164
167
165
-
In this lab, you learned how to convert classic pipelines into YAML-based ones and how to implement and use self-hosted agents.
168
+
In this lab, you learned how to implement and use self-hosted agents with YAML pipelines.
0 commit comments