actions/importer-labs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Reorder the migrate and forecast labs

Browse Source
This commit is contained in:
Ethan Dennis
2022-09-06 11:16:27 -07:00
parent 058b33e146
commit 3af1b57306
4 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
jenkins/4-custom-transformers.md
+1 -1
View File
@@ -318,4 +318,4 @@ Thats it! Congratulations you have overridden Valet's default behavior by custom
## Next lab ## Next lab
[Forecast Jenkins Usage](../jenkins/5-forecast.md#forecast-the-runner-usage-of-a-jenkins-instance) [Perform a production migration of a Jenkins pipeline](5-migrate.md)
jenkins/6-migrate.md → jenkins/5-migrate.md
View File
jenkins/5-forecast.md → jenkins/6-forecast.md
View File
jenkins/readme.md
+2 -2
View File
@@ -58,8 +58,8 @@ Perform the following labs to test-drive Valet
2. [Perform an audit of a Jenkins server](2-audit.md) 2. [Perform an audit of a Jenkins server](2-audit.md)
3. [Perform a dry-run of a Jenkins pipeline](3-dry-run.md) 3. [Perform a dry-run of a Jenkins pipeline](3-dry-run.md)
4. [Use custom transformers to customize Valet's behavior](4-custom-transformers.md) 4. [Use custom transformers to customize Valet's behavior](4-custom-transformers.md)
5. [Forecast potential build runner usage](5-forecast.md) 5. [Perform a production migration of a Jenkins pipeline](5-migrate.md)
6. [Perform a production migration of a Jenkins pipeline](6-migrate.md) 6. [Forecast potential build runner usage](6-forecast.md)
## Troubleshoot the Valet CLI ## Troubleshoot the Valet CLI