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 Jenkins 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 a new Codespace.

Click the Code with button down arrow above repository on the 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.

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 version did not produce similar output then please follow the troubleshooting guide.

Bootstrap a Jenkins server

Execute the Jenkins setup script that will start a container with a Jenkins server running inside of it. This script should be executed when starting a new Codespace or restarting an existing one.

Run the following command from the codespace's terminal to start a Jenkins server:
```
./jenkins/bootstrap/setup.sh
```
After some time, a pop-up box should appear with a link to the URL for your Jenkins server.
- You can also access the URL by going to the Ports tab in your terminal. Right click on the URL listed under the Local Address and click the Open in Browser tab.

Open the Jenkins server in your browser and use the following credentials to authenticate:

Username: admin
Password: password
Once authenticated, you should see a Jenkins server with a few predefined pipelines.

Labs for Jenkins

Perform the following labs to learn more about Actions migrations with Valet:

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.
- Restart the codespace after clicking the link.
Verify Valet CLI extension is installed and working by running the following command from the codespace's terminal:
```
gh valet version
```

Troubleshooting the Jenkins server

Follow these steps if the Jenkins server does not start correctly after running the setup script:

Navigate to the Docker tab on the left side of the codespace.
Under the Containers tab you should see a docker container named jenkins:valet listed with a green play button ▶

If you see the jenkins:valet container, but it has a red stopped symbol next to it ▢, right click on the container and click on start, the container should begin running again.
If the container does not start even after trying to manually start it, right click on the jenkins:valet container and click the remove button. Then, attempt to start the Jenkins server again by following the steps here.