importer-labs/gitlab/valet-migrate-lab.md

Migrate an Azure DevOps pipeline to GitHub Actions

In this lab, we will use the Valet migrate command to migrate a GitLab pipeline to GitHub Actions. All of the previous commands we have been using in the labs, such as audit and dry-run have been preparing us to run a migration. The migrate command will generate the GitHub Actions workflow files, like the dry-run did, and also create a pull request with the files.
The pull request will also contain a checklist of Manual Tasks if required. These tasks are changes that Valet could not do on our behalf, like creating a runner or adding a secret to a repository.

• Prerequisites
• Preparing for migration
• Performing the migration
• Reviewing the pull request
• Next Lab

Prerequisites

1. Followed steps to set up your codespace environment.
2. Completed the configure lab

Preparing for migration

Before running the command we need to collect some information:

1. What is the project we want to migrate? rails-example
2. What is the namespace for that project? Valet. In this case the namespace is the same as the group the project is in
3. Where do we want to store the logs? ./tmp/migrate.
4. What is the URL for GitHub repository we want to add the workflow too? this repo!. When constructing the value for the migrate command it should match this url https://github.com/GITHUB-ORG-USERNAME-HERE/GITHUB-REPO-NAME-HERE with GITHUB-ORG-USERNAME and GITHUB-REPO-NAME substitued with your values

Performing a migration

1. Run migrate command using the information collected above, make sure to update the --target-url value with the information from step 4.

gh valet migrate gitlab --target-url https://github.com/GITHUB-ORG-USERNAME-HERE/GITHUB-REPO-NAME-HERE --output-dir ./tmp/migrate --namespace valet --project rails-example

2. Valet will create a pull request directly in the target GitHub repository.
3. Open the pull request by clicking the green pull request link in the output of the migrate command, if you have trouble clicking it you can always copy and paste the url in your browser.

Reviewing the pull request

• Lets first look at the Conversation tab of the PR. It tells us we have a manual task to perform before the GitHub Actions workflow is functional. We need to a secret. We can use the GitHub documentation for secrets and add a actions secret for PASSWORD with any value.

• Next, lets review the workflow we are adding by clicking on Files changed tab. This is where you would double check everything looks good.

• Now our review is completed we want to go back to the Conversation tab and click Merge pull request

• Once the PR is merged the new workflow should start and we can view it by clicking Actions in the top navigation

Next Lab

Forecast GitLab Usage