actions/importer-labs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Readme edits

Browse Source
This commit is contained in:
Jennifer Kerns
2022-09-13 08:55:51 -04:00
committed by GitHub
parent 15d5df048d
commit a3f2fe338f
22 changed files with 287 additions and 287 deletions
Download Patch File Download Diff File Expand all files Collapse all files
azure_devops/readme.md
+15 -15
View File
@@ -1,25 +1,25 @@
# Azure Pipelines to Actions migrations powered by Valet
The instructions below will guide you through configuring a Codespace that will be used in these labs to demonstrate how Valet can be used to migrate Azure DevOps pipelines to GitHub Actions.
These instructions will guide you through configuring the GitHub Codespaces environment that will be used in these labs to demonstrate how to use Valet to migrate Azure DevOps pipelines to GitHub Actions.
These steps **must** be completed prior to starting other labs.
## Create your own repository for these labs
1. Ensure that you have created a repository using the [valet-customers/labs](https://github.com/valet-customers/labs) as a template.
- Ensure that you have created a repository using [valet-customers/labs](https://github.com/valet-customers/labs) as a template.
## Configure your Codespace
## Configure your codespace
1. Start a new Codespace.
1. Start a new codespace.
- Click the `Code` button on your repository's landing page.
- Click the `Codespaces` tab.
- Click `Create codespaces on main` to create the codespace.
- After the Codespace has initialized there will be a terminal present.
- After the codespace has initialized there will be a terminal present.
2. Verify the Valet CLI is installed and working. More information on the Valet extension for the official GitHub CLI can be found [here](https://github.com/github/gh-valet).
- Run the following command in the codespace's terminal:
- Run the following command in the codespace terminal:
```bash
gh valet version
@@ -33,14 +33,14 @@ These steps **must** be completed prior to starting other labs.
valet-cli unknown
```
- If `gh valet version` did not produce similar output then please follow the troubleshooting [guide](#troubleshoot-the-valet-cli).
- If `gh valet version` did not produce similar output, please refer to the troubleshooting [guide](#troubleshoot-the-valet-cli).
## Bootstrap your Azure DevOps organization
1. Create an Azure DevOps personal access token:
1. Create an Azure DevOps personal access token (PAT):
- Navigate to your existing organization (<https://dev.azure.com/:organization>) in your browser.
- Click `User settings` in the top right corner of the screen.
- In the top right corner of the screen, click `User settings`.
- Click `Personal access tokens`.
- Select `+ New Token`
- Name your token, select the organization where you want to use the token, and set your token to automatically expire after a set number of days.
@@ -54,11 +54,11 @@ These steps **must** be completed prior to starting other labs.
- Task Groups: `Read`
- Variable Groups: `Read`
- Click `Create`.
- Copy the generated API token and save in a safe location.
- Copy the generated API token and save it in a safe location.
2. Execute the Azure DevOps setup script that will create a new Azure DevOps project in your organization to be used in the following labs. This script should only be run once.
- Run the following command from the codespace's terminal, replacing the values accordingly:
- Run the following command from the codespace terminal, replacing the values accordingly:
- `:organization`: the name of your existing Azure DevOps organization
- `:project`: the name of the project to be created in your Azure DevOps organization
- `:access_token`: the PAT created in step 1 above
@@ -77,7 +77,7 @@ Perform the following labs to learn how to migrate Azure DevOps pipelines to Git
1. [Configure credentials for Valet](1-configure.md)
2. [Perform an audit of an Azure DevOps project](2-audit.md)
3. [Perform a dry-run of a Azure DevOps pipeline](3-dry-run.md)
3. [Perform a dry-run migration of an Azure DevOps pipeline](3-dry-run.md)
4. [Use custom transformers to customize Valet's behavior](4-custom-transformers.md)
5. [Perform a production migration of a Azure DevOps pipeline](5-migrate.md)
6. [Forecast potential build runner usage](6-forecast.md)
@@ -87,7 +87,7 @@ Perform the following labs to learn how to migrate Azure DevOps pipelines to Git
The CLI extension for Valet can be manually installed by following these steps:
- Verify you are in the codespace terminal
- Run this command from within the codespace's terminal:
- Run this command from within the codespace terminal:
```bash
gh extension install github/gh-valet
@@ -99,10 +99,10 @@ The CLI extension for Valet can be manually installed by following these steps:
✓ Installed extension github/gh-valet
```
- If you get an error similar to the image below, then click the link in the terminal output to authorize the token.
- If you get an error similar to the image below, click the link in the terminal output to authorize the token.
- Restart the codespace after clicking the link.
![img](https://user-images.githubusercontent.com/26442605/169588015-9414404f-82b6-4d0f-89d4-5f0e6941b029.png)
- Verify Valet CLI extension is installed and working by running the following command from the codespace's terminal:
- Verify Valet CLI extension is installed and working by running the following command from the codespace terminal:
```bash
gh valet version