* Update readme.md * Update readme.md * Update readme.md * Update devcontainer.json * Update setupcodespace.sh * Update valet-audit-lab.md * Update valet-dry-run-lab.md * Update valet-migrate-lab.md * Update valet-migrate-custom-lab.md * Update valet-audit-lab.md * Update valet-audit-lab.md * Update valet-dry-run-lab.md * Update valet-migrate-lab.md * Update valet-migrate-custom-lab.md * Update valet-dry-run-lab.md * Update valet-migrate-custom-lab.md
53 lines
2.2 KiB
Markdown
53 lines
2.2 KiB
Markdown
# Dry run the migration of an Azure DevOps pipeline to GitHub Actions
|
|
In this lab, you will use the `valet dry-run` command to convert an Azure DevOps pipeline to it's equivalent GitHub Actions workflow and write the workflow to your local filesystem.
|
|
|
|
- [Prerequisites](#prerequisites)
|
|
- [Identify the Azure DevOps pipeline ID to use](#identify-the-azure-devops-pipeline-id-to-use)
|
|
- [Perform a dry run](#perform-a-dry-run)
|
|
- [View dry-run output](#view-dry-run-output)
|
|
- [Next Lab](#next-lab)
|
|
|
|
## Prerequisites
|
|
|
|
1. Follow all steps [here](../azure_devops#readme) to set up your environment
|
|
2. Create or start a codespace in this repository (if not started)
|
|
3. You have completed the [Valet audit lab](valet-audit-lab.md).
|
|
|
|
## Identify the Azure DevOps pipeline ID to use
|
|
You will need a pipeline ID to perform the dry run
|
|
1. Go to the `valet/ValetBootstrap/pipelines` folder
|
|
2. Open the `valet/ValetBootstrap/pipelines/valet-pipeline1.config.json` file
|
|
3. Look for the `$.web.href` link
|
|
4. At the end of the link is the pipeline ID. Copy or note the ID.
|
|
|
|
### Example
|
|

|
|
|
|
## Perform a dry run
|
|
You will use the codespace preconfigured in this repository to perform the dry run.
|
|
|
|
1. Navigate to the codespace Visual Studio Code terminal
|
|
2. Verify you are in the `valet` directory
|
|
|
|
```
|
|
gh valet dry-run azure-devops pipeline --pipeline-id PIPELINE-ID --output-dir dry-run
|
|
```
|
|
3. Now, from the `valet` folder in your repository, run `gh valet dry-run` to see the output:
|
|
|
|
### Example
|
|

|
|
|
|
4. Valet will create a folder called `dry-runs` under the `valet` folder that shows what will be migrated.
|
|
|
|
### Example
|
|

|
|
|
|
## View dry-run output
|
|
The dry-run output will show you the GitHub Actions yml that will be migrated to GitHub.
|
|
|
|
### Example
|
|

|
|
|
|
### Next Lab
|
|
[Migrate an Azure DevOps pipeline to GitHub Actions](valet-migrate-lab.md)
|