Skip to content

Commit 38ba17f

Browse files
Merge pull request #50222 from ShawnKupfer/WB1764
Fix DevOps Demo Generator and add Fork
2 parents 4feef4b + 6556e31 commit 38ba17f

File tree

1 file changed

+21
-13
lines changed

1 file changed

+21
-13
lines changed

learn-pr/azure-devops/run-quality-tests-build-pipeline/includes/3-set-up-environment.md

Lines changed: 21 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -13,26 +13,34 @@ Here, you'll make sure that your Azure DevOps organization is set up to complete
1313

1414
### Run the template
1515

16-
Run a template that sets up everything for you in your Azure DevOps organization.
16+
Run a template that sets up your Azure DevOps organization.
1717

18-
> [!div class="nextstepaction"]
19-
> [Run the template](https://azuredevopsdemogenerator.azurewebsites.net/?x-ms-routing-name=self&name=run-quality-tests&azure-portal=true)
18+
1. [Get and run the ADOGenerator project](https://github.com/microsoft/AzDevOpsDemoGenerator/blob/main/docs/RunApplication.md) in Visual Studio or the IDE of your choice.
2019

21-
To run the template, on the Azure DevOps Demo Generator site, do the following:
20+
1. When prompted to **Enter the template number from the list of templates**, enter **24** for **Run quality tests in your build pipeline using Azure Pipelines**, then press **Enter**.
2221

23-
1. Select **Sign In** and accept the usage terms.
24-
1. On the **Create New Project** page, select your Azure DevOps organization, and then enter a project name, such as *Space Game - web - Tests*.
25-
1. Select the box next to **Yes, I want to fork this repository**, then select **Authorize**. If a window appears, authorize access to your GitHub account.
22+
1. Choose your authentication method. You can [set up and use a Personal Access Token (PAT)](/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate#create-a-pat) or use device login.
2623

27-
> [!IMPORTANT]
28-
> You need to select this option for the template to connect to your GitHub repository. Select it even if you've already forked the _Space Game_ website project. The template uses your existing fork.
24+
> [!NOTE]
25+
> If you set up a PAT, If you set up a PAT, make sure to authorize the necessary [scopes](/azure/devops/integrate/get-started/authentication/oauth#scopes). For this module, you can use **Full access**, but in a real-world situation, you should ensure you grant only the necessary scopes.
2926
30-
1. Select **Create Project**.
27+
1. Enter your Azure DevOps organization name, then press **Enter**.
3128

32-
:::image type="content" source="../media/3-create-new-project.png" alt-text="A screenshot of the Azure DevOps Demo Generator Create New Project screen with the Create Project button highlighted.":::
29+
1. If prompted, enter your Azure DevOps PAT, then press **Enter**.
3330

34-
It takes a few moments for the template to run.
35-
1. Select **Navigate to project** to go to your project in Azure DevOps.
31+
1. Enter a project name such as *Space Game - web - Tests*, then press **Enter**.
32+
33+
1. Once your project is created, go to your Azure DevOps organization in your browser (at `https://dev.azure.com/<your-organization-name>/`) and select the project.
34+
35+
## Fork the repository
36+
37+
If you haven't already, create a fork of the **mslearn-tailspin-spacegame-web** repository.
38+
39+
1. On GitHub, go to the [mslearn-tailspin-spacegame-web](https://github.com/MicrosoftDocs/mslearn-tailspin-spacegame-web) repository.
40+
41+
1. Select **Fork** at the top-right of the screen.
42+
43+
1. Choose your GitHub account as the **Owner**, then select **Create fork**.
3644

3745
> [!IMPORTANT]
3846
> The [Clean up your Azure DevOps environment](/training/modules/run-quality-tests-build-pipeline/8-clean-up-environment?azure-portal=true) page in this module contains important cleanup steps. Cleaning up helps ensure that you don't run out of free build minutes. Be sure to perform the cleanup steps even if you don't complete this module.

0 commit comments

Comments
 (0)