Skip to content
This repository was archived by the owner on Nov 14, 2025. It is now read-only.

Conversation

@unaihuete93
Copy link
Contributor

Module: 5

Lab/Demo: Lab: Configuring Agent Pools and Understanding Pipeline Styles

Changes proposed in this pull request:

  • use the LAB VM (LOD) instead of Azure VM, making the lab easier for the concepts we want to be showing

Copy link

@ClementinoDeMendonca-msft ClementinoDeMendonca-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Unai, please take a look at the suggestions below.

New-Item -Type Directory -Path 'C:\agent'
Set-Location -Path 'C:\agent'
Add-Type -AssemblyName System.IO.Compression.FileSystem
[System.IO.Compression.ZipFile]::ExtractToDirectory("$HOME\Downloads\vsts-agent-win-x64-2.179.0.zip", "$PWD")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of "2.179.0", there should be a placeholder for the version. The download file version will change frequently.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done :)

| ------- | ----- |
| Enter server URL | the URL of your Azure DevOps organization, in the format **https://dev.azure.com/`<organization_name>`**, where `<organization_name>` represents the name of your Azure DevOps organization |
| Enter authentication type (press enter for PAT) | **Enter** key |
| Enter personal access token | the access token you recorded earlier in this task |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not your change, but in the previous line, "Enter key" should be just Enter. Also, what do and Michael think about saying "Press Enter" instead. It wasn't clear to some students what "Enter" meant.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done :)

1. On the **az400m05-vm0** blade, click **Connect**, in the dropdown list, click **RDP**, on the **az400m05-vm0 \| Connect** blade, click **Download RDP File** and open the downloaded RDP file to connect to the **az400m05-vm0** Azure VM by using Remote Desktop. When prompted to sign in, provide the **Student** as the user name and **Pa55w.rd1234** as the password.
1. Within the Remote Desktop session to **az400m05-vm0**, start a web browser, navigate to [the Azure DevOps portal](https://dev.azure.com) and sign in by using the Microsoft account associated with your Azure DevOps organization.
1. In the Azure DevOps portal, close the **Get the agent** panel, in the upper right corner of the Azure DevOps page, click the **User settings** icon, in the dropdown menu, click **Personal access tokens**, on the **Personal Access Tokens** pane, and click **+ New Token**.
1. Within the LOD VM (Lab VM), start a web browser, navigate to [the Azure DevOps portal](https://dev.azure.com) and sign in by using the Microsoft account associated with your Azure DevOps organization.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's replace "LOD VM" by just "Lab Virtual machine (Lab VM) or your own computer". This lab should not depend on a particular vendor VM or being on a VM at all.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done :)

1. Back on the **Create New Project** page, select the checkbox below the **ARM Outputs** label, and click **Create Project**

> **Note**: Wait for the process to complete. This should take about 2 minutes. In case the process fails, navigate to your DevOps organization, delete the project, and try again.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment is not related to this line, but to the line above "Estimated time: 90 minutes". Could you switch it to "45 minutes" (It was actually less when tested in class).

Also the whole sections above on "Prepare an Azure subscription" and "Set up a GitHub account" are not needed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done :)

| Enter work folder (press enter for _work) | **C:\agent** |
| Enter work folder (press enter for _work) | **Enter** |
| Enter Perform an unzip for tasks for each step. (press enter for N) | **Enter** |
| Enter run agent as service? (Y/N) (press enter for N) | **Enter** |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer saying Y have it run as a service, in case the student needs to reboot the VM. Choose so also makes unnecessary the next question on autologon.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done :)

1. In the Azure DevOps portal, in the vertical navigational pane on the left side, in the **Pipelines** section, click **Pipelines**.
1. On the **Recent** tab of the **Pipelines** pane, click the **PartsUnlimitedE2E** entry.
1. On the **Runs** tab of the **PartsUnlimitedE2E** pane, in the upper right corner, click the vertical ellipsis symbol and, in the dropdown menu, click **Export to YAML**. This will automatically download the **build.yml** file to your local **Downloads** folder.
1. On the **Runs** tab of the **PartsUnlimitedE2E** pane, in the upper right corner, click the vertical ellipsis (three vertical dots) symbol and, in the dropdown menu, click **Export to YAML**. This will automatically download the **build.yml** file to your local **Downloads** folder.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The exported yaml file is actually called "PartsUnlimitedE2E.yml" not "build.yml".

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done :)

@unaihuete93
Copy link
Contributor Author

All fixes proposed in comments added 👍 @ClementinoDeMendonca-msft

Copy link

@ClementinoDeMendonca-msft ClementinoDeMendonca-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you Unai, this will expedite doing this lab, allowing students to focus on Azure DevOps instead of a side topic on creating a virtual machine. At that the first part was more of an AZ-104 lab.

@unaihuete93
Copy link
Contributor Author

conflict resolved, we should be able to approve the PR now :)

@unaihuete93
Copy link
Contributor Author

Added Preethi´s proposals from MS Teams chat

@mkennten mkennten merged commit c76d35b into MicrosoftLearning:master Feb 20, 2021
@unaihuete93 unaihuete93 deleted the lab5-proposal-unai branch March 16, 2021 09:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants