Skip to content

Commit e291bbc

Browse files
author
gitName
committed
Fix DevOps Demo Generator
1 parent 5639745 commit e291bbc

File tree

1 file changed

+21
-10
lines changed

1 file changed

+21
-10
lines changed

learn-pr/azure-devops/manage-release-cadence/includes/3-set-up-environment.md

Lines changed: 21 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -32,21 +32,32 @@ The modules in this learning path are part of a progression. You follow the Tail
3232

3333
Run a template that sets up your Azure DevOps organization.
3434

35-
> [!div class="nextstepaction"]
36-
> [Run the template](https://azuredevopsdemogenerator.azurewebsites.net/?x-ms-routing-name=self&name=manage-release-cadence&azure-portal=true)
35+
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.
3736

38-
On the Azure DevOps Demo Generator site, follow these steps to run the template:
37+
1. When prompted to **Enter the template number from the list of templates**, enter **34** for **Manage release cadence in Azure Pipelines with deployment patterns**, then press **Enter**.
3938

40-
1. Select **Sign In** and accept the usage terms.
41-
1. On the **Create New Project** page, select your Azure DevOps organization. Then enter a project name, such as *Space Game - web - Deployment patterns*.
39+
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.
4240

43-
:::image type="content" source="../media/3-create-new-project.png" alt-text="Screenshot that shows how to create a project through the Azure DevOps Demo Generator.":::
41+
> [!NOTE]
42+
> 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.
4443
45-
1. Select **Yes, I want to fork this repository**. Then select **Authorize**.
46-
1. Select **Create Project**.
44+
1. Enter your Azure DevOps organization name, then press **Enter**.
4745

48-
The template takes a few moments to run.
49-
1. Select **Navigate to project** to go to your project in Azure DevOps.
46+
1. If prompted, enter your Azure DevOps PAT, then press **Enter**.
47+
48+
1. Enter a project name such as *Space Game - web - Deployment patterns*, then press **Enter**.
49+
50+
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.
51+
52+
### Fork the repository
53+
54+
If you haven't already, create a fork of the **mslearn-tailspin-spacegame-web-deploy** repository.
55+
56+
1. On GitHub, go to the [mslearn-tailspin-spacegame-web-deploy](https://github.com/MicrosoftDocs/mslearn-tailspin-spacegame-web-deploy) repository.
57+
58+
1. Select **Fork** at the top-right of the screen.
59+
60+
1. Choose your GitHub account as the **Owner**, then select **Create fork**.
5061

5162
> [!IMPORTANT]
5263
> The [Clean up your Azure DevOps environment](/training/modules/manage-release-cadence/6-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 follow the cleanup steps even if you don't complete this module.

0 commit comments

Comments
 (0)