importer-labs/jenkins

Valet labs for Jenkins

This lab bootstraps a Valet environment using GitHub Codespaces and enables you to spin up a Jenkins instance against which to run the Valet CI/CD migration tool.

• Use this repo as a template
• Use Valet with a codespace
• Bootstrap Jenkins
• Labs for Jenkins
• Troubleshoot GH Valet extension
• Troubleshooting Jenkins

Repo template

1. Verify you are in your own Repository created from the landing page Valet Labs.

Use Valet with a codespace

1. Start the 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. If you are in another branch then the main branch, the codespace will button will have the current branch specified.
   • Wait a couple minutes, then verify that the codespace starts up. Once it is fully booted up, the termininal should be present.
2. Verify Valet CLI is installed and working. More information on the GitHub Valet CLI extension

   • Verify Valet CLI is installed and working

   • Run the following command in the Visual Studio Code terminal:

     gh valet version
     

   • Verify the output looks like the below image. Note the valet version will be different than below as the latest version gets pulled down.

     • If gh valet version did not produce a similar image with a version please follow these instructions Troubleshoot GH Valet extension

Bootstrap Jenkins

1. Run the Jenkins setup script. This script will setup Jenkins and ensure it is ready to use. In general, this script should be run first if you are starting a new codespace or restarting an existing one.

• Navigate to the terminal within your Codespace.

• Run the following command to kick off the creation of your Jenkins instance:

  source jenkins/bootstrap/setup.sh
  

• After a couple seconds, a pop-up box should appear with a link to the forwarded URL for your Jenkins instance.

• You can also access the forwarded URL by going to the Ports tab in your terminal. Right click on the URL listed under the Local Address and clicking the Open in Browser tab.

• Once you have navigated to the url, the following default credentials have been assigned:

  • username: admin
  • password: password

2. Click the Sign in button and you should now see your new Jenkins instance with a few pre-populataed pipelines.

Labs for Jenkins

Perform the following labs to test-drive Valet

• Configure Valet to work with Jenkins
• Audit Jenkins using the Valet audit command
• Dry-run the migration of an Jenkins pipeline to GitHub Actions
• Using Custom Transformers in a dry-run
• Migrate an Jenkins Project to GitHub Actions
• Forecast the usage of a Jenkins namespace

Troubleshoot GH Valet extension

Manually Install the GitHub CLI Valet extension. More information on the GitHub Valet CLI extension

• Verify you are in the codespace terminal

• Run this command to install the GitHub Valet extension

• gh extension install github/gh-valet

• Verify the result of the install is: ✓ Installed extension github/gh-valet

• If you get a similiar error to the following, click the link to authorize the token

  • Restart Codespace after clicking the link

• Verify Valet CLI is installed and working by running gh valet version

  

Troubleshooting Jenkins

1. Navigate to the Docker tab on your left hand side.
2. Under the Containers tab you should see a Docker container 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. Next continue by following all the #bootstrap-jenkins instructions again.