importer-labs/azure_devops/5-migrate.md

Perform a production migration of an Azure DevOps pipeline

In this lab, you will use the migrate command to convert an Azure DevOps pipeline and open a pull request with the equivalent Actions workflow.

Prerequisites

1. Followed the steps here to set up your Codespace environment and bootstrap an Azure DevOps project.
2. Completed the configure lab.
3. Completed the dry-run lab.
4. Completed the custom transformers lab.

Performing a migration

We need to answer the following questions before running a migrate command:

1. What is the id of the pipeline to convert?
   • :pipeline_id. This id can be found by:
     • Navigating to the build pipelines in the bootstrapped Azure DevOps project https://dev.azure.com/:organization/:project/_build
     • Selecting the pipeline with the name "valet-custom-transformer-example"
     • Inspecting the URL to locate the pipeline id https://dev.azure.com/:organization/:project/_build?definitionId=:pipeline_id
2. Where do we want to store the logs?
   • ./tmp/migrate
3. What is the URL for the GitHub repository to add the workflow to?
   • this repository. The URL should should follow the pattern https://github.com/:owner/:repo with :owner and :repo replaced with your values.

Steps

1. Run the following migrate command in the codespace terminal:

   gh valet migrate azure-devops pipeline --pipeline-id :pipeline_id --target-url https://github.com/:owner/:repo --output-dir ./tmp/migrate
   

2. The command will write the URL to the pull request that was created when the command succeeds.

   ➜ gh valet migrate azure-devops pipeline --pipeline-id 7 --target-url https://github.com/ethanis/labs --output-dir ./tmp/migrate
   [2022-09-07 20:25:08] Logs: 'tmp/dry-run-lab/log/valet-20220907-202508.log'
   [2022-09-07 20:25:13] Pull request: 'https://github.com/ethanis/labs/pull/42'
   

3. Open the generated pull request in a new browser tab.

Inspect the pull request

The first thing we should notice about the PR is that there is a list of manual steps for us to complete:

Next, let's review the workflow we are adding by clicking on Files changed tab. This is where you would double check everything looks good. If it didn't you could push commits with the required changes, prior to merging.

Next, you can inspect the "Files changed" in this PR and see the converted workflow that is being added. Any additional changes or code reviews that were needed should be done in this PR.

Finally, you can merge the PR once your review has completed. We can then view the workflow running by selecting the "Actions" menu in the top navigation bar in GitHub.

At this point, the migration has completed and you have successfully migrated an Azure DevOps pipeline to Actions!

Next lab

Forecast potential build runner usage