GitLab to Actions migrations powered by Valet
The instructions below will guide you through configuring a GitHub Codespace environment that will be used in subsequent labs that demonstrate how to use Valet to migrate GitLab pipelines to GitHub Actions.
These steps must be completed prior to starting other labs.
Create your own repository for these labs
- Ensure that you have created a repository using the valet-customers/labs as a template.
Configure your Codespace
- Start the codespace
- Click the
Codebutton down arrow above the repository on the repository's landing page. - Click the
Codespacestab. - Click
Create codespaces on mainto create the codespace. - After the Codespace has initialized there will be a terminal present.
- Verify the Valet CLI is installed and working. More information on the Valet extension for the official GitHub CLI can be found here.
-
Run the following command in the codespace's terminal:
gh valet version -
Verify the output is similar to below.
gh version 2.14.3 (2022-07-26) gh valet github/gh-valet v0.1.12 valet-cli unknown- If
gh valet versiondid not produce similar output then please follow the troubleshooting guide.
- If
Bootstrap a GitLab Server
- Execute the GitLab setup script that will start a container with a GitLab server running inside of it. The script should be executed when starting a new Codespace or restarting an existing one.
-
Run the following command from the codespace's terminal
source gitlab/bootstrap/setup.sh
- Wait for the script to finish and then verify you can login to the GitLab Server.
- Click the
PORTStab in the codespace terminal window. - In the row that starts with
80mouse over the address under the column headingLocal Address, and click the globe icon. - Verify a new browser tab opened to the GitLab login screen.
- Login using the following credentials:
- Username:
root - Password:
valet-labs!
- Username:
- Verify that you can see the auto populated projects in GitLab, under the
valetnamespace by clicking theMenuicon in GitLab, thenYour projects.
Labs for GitLab
Perform the following labs to test-drive Valet
- Configure credentials for Valet
- Perform an audit on GitLab pipelines
- Perform a dry-run of a GitLab pipeline
- Use custom transformers to customize Valet's behavior
- Forecast potential build runner usage
- Perform a production migration of a GitLab pipeline
Troubleshoot the Valet CLI
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:
gh extension install github/gh-valet -
Verify the result of the install contains:
✓ 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.
-
Verify Valet CLI extension is installed and working by running the following command from the codespace's terminal:
gh valet version
