All links are clickable and go to the tops of pages

This commit is contained in:
Begona Guereca
2022-08-25 12:59:38 -07:00
parent 83f2c00251
commit 1f16644413
5 changed files with 17 additions and 13 deletions
+7 -3
View File
@@ -2,7 +2,7 @@
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. 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](#repo-template) - [Use this repo as a template](#repo-template)
- [Prerequisites](#prerequisites) - [Prerequisites](#prerequisites)
- [Use Valet with a codespace](#use-valet-with-a-codespace) - [Use Valet with a codespace](#use-valet-with-a-codespace)
- [Bootstrap Jenkins](#bootstrap-jenkins) - [Bootstrap Jenkins](#bootstrap-jenkins)
@@ -11,7 +11,6 @@ This lab bootstraps a Valet environment using GitHub Codespaces and enables you
1. Verify you are in your own Repository created from the landing page [Valet Labs](https://github.com/valet-customers/labs). 1. Verify you are in your own Repository created from the landing page [Valet Labs](https://github.com/valet-customers/labs).
## Use Valet with a codespace ## Use Valet with a codespace
1. Start the codespace 1. Start the codespace
@@ -45,7 +44,12 @@ This lab bootstraps a Valet environment using GitHub Codespaces and enables you
Perform the following labs to test-drive Valet Perform the following labs to test-drive Valet
- TBD - [Configure Valet to work with Jenkins](valet-configure-lab.md#configure-valet-to-work-with-jenkins)
- [Audit Jenkins using the Valet audit command](valet-audit-lab.md#audit-jenkins-pipelines-using-the-valet-audit-command)
- [Dry run the migration of an Jenkins pipeline to GitHub Actions](valet-dry-run-lab.md#dry-run-the-migration-of-a-jenkins-pipeline-to-github-actions)
- [Using Custom Transformers in a dry-run](valet-custom-transformers-lab.md#using-custom-transformers-in-a-dry-run)
- [Migrate an Jenkins Project to GitHub Actions](valet-migrate-lab.md#migrate-a-jenkins-project-to-github-actions)
- [Forecast the usage of a Jenkins namespace](valet-forecast-lab.md#forecast-the-runner-usage-of-a-jenkins-instance)
## Troubleshoot GH Valet extension ## Troubleshoot GH Valet extension
+2 -2
View File
@@ -9,7 +9,7 @@ In this lab, you will use the Valet `configure` command to set up the required i
## Prerequisites ## Prerequisites
1. Followed [steps](../Jenkins#readme) to set up your codespace environment and start your Jenkins instanace. 1. Followed [steps](../jenkins/readme.md) to set up your codespace environment and start your Jenkins instanace.
## Configuring Valet ## Configuring Valet
@@ -75,4 +75,4 @@ To verify Valet works we are going to run a `update` and `dry-run` command. We
### Next Lab ### Next Lab
[Dry-run Jenkins Pipelines to a GitHub Action Workflow](../Jenkins/valet-dry-run-lab.md) [Dry-run Jenkins Pipelines to a GitHub Action Workflow](../jenkins/valet-dry-run-lab.md#dry-run-the-migration-of-a-jenkins-pipeline-to-github-actions)
+1 -1
View File
@@ -398,4 +398,4 @@ Thats it! Congratulations you have customized transforming:
## Next Lab ## Next Lab
[Migrating a Jenkins Pipeline](../jenkins/valet-migrate-lab.md) [Migrating a Jenkins Pipeline](../jenkins/valet-migrate-lab.md#migrate-a-jenkins-project-to-github-actions)
+2 -2
View File
@@ -1,4 +1,4 @@
# Dry run the migration of an Jenkins pipeline to GitHub Actions # Dry run the migration of a Jenkins pipeline to GitHub Actions
In this lab, you will use the Valet `dry-run` command to convert a Jenkins pipeline to its equivalent GitHub Actions workflow. In this lab, you will use the Valet `dry-run` command to convert a Jenkins pipeline to its equivalent GitHub Actions workflow.
The end result of this command will be the actions workflow written to your local filesystem. The end result of this command will be the actions workflow written to your local filesystem.
@@ -180,4 +180,4 @@ Try constructing and running the `dry-run` command yourself. Hint, you should ju
## Next Lab ## Next Lab
TODO [Using Custom Transformers in a dry-run](valet-custom-transformers-lab.md#using-custom-transformers-in-a-dry-run)
+3 -3
View File
@@ -1,4 +1,4 @@
# Migrate an Jenkins Project to GitHub Actions # Migrate a Jenkins Project to GitHub Actions
In this lab, we will use the Valet `migrate` command to migrate a Jenkins pipeline to GitHub Actions. In this lab, we will use the Valet `migrate` command to migrate a Jenkins pipeline to GitHub Actions.
The previous commands used in the labs, such as `audit` and `dry-run` have prepared us to run a migration. The previous commands used in the labs, such as `audit` and `dry-run` have prepared us to run a migration.
@@ -13,7 +13,7 @@ The pull request will contain a checklist of `Manual Tasks` if required. These t
## Prerequisites ## Prerequisites
1. Followed [steps](../jenkins#readme) to set up your codespace environment. 1. Followed [steps](../jenkins/readme.md) to set up your codespace environment.
2. Completed the [configure lab](../jenkins/valet-configure-lab.md) 2. Completed the [configure lab](../jenkins/valet-configure-lab.md)
3. Completed the [dry-run lab](../jenkins/valet-dry-run-lab.md) 3. Completed the [dry-run lab](../jenkins/valet-dry-run-lab.md)
4. Completed the [dry-run lab with custom transformer](../jenkins/valet-custom-transformers-lab.md) 4. Completed the [dry-run lab with custom transformer](../jenkins/valet-custom-transformers-lab.md)
@@ -53,4 +53,4 @@ gh valet migrate jenkins --target-url https://github.com/GITHUB-ORG-USERNAME-HER
### Next Lab ### Next Lab
[Forecast Jenkins Usage](../Jenkins/valet-forecast-lab.md) [Forecast Jenkins Usage](../jenkins/valet-forecast-lab.md#forecast-the-runner-usage-of-a-jenkins-instance)