From 38073eea5446ba2d1edcc841a7480c4f21cdc906 Mon Sep 17 00:00:00 2001 From: Ethan Dennis Date: Wed, 14 Sep 2022 12:31:02 -0700 Subject: [PATCH] Reorder jenkins labs --- jenkins/2-audit.md | 2 +- jenkins/{6-forecast.md => 3-forecast.md} | 2 +- jenkins/{3-dry-run.md => 4-dry-run.md} | 2 +- jenkins/{4-custom-transformers.md => 5-custom-transformers.md} | 2 +- jenkins/{5-migrate.md => 6-migrate.md} | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) rename jenkins/{6-forecast.md => 3-forecast.md} (98%) rename jenkins/{3-dry-run.md => 4-dry-run.md} (98%) rename jenkins/{4-custom-transformers.md => 5-custom-transformers.md} (99%) rename jenkins/{5-migrate.md => 6-migrate.md} (97%) diff --git a/jenkins/2-audit.md b/jenkins/2-audit.md index c3e9a6c..e2c8b35 100644 --- a/jenkins/2-audit.md +++ b/jenkins/2-audit.md @@ -108,4 +108,4 @@ Each pipeline will have a variety of files written that include: ## Next lab -[Perform a dry-run migration of a Jenkins pipeline](3-dry-run.md) +[Forecast potential build runner usage](3-forecast.md) diff --git a/jenkins/6-forecast.md b/jenkins/3-forecast.md similarity index 98% rename from jenkins/6-forecast.md rename to jenkins/3-forecast.md index a6fca52..7748a1f 100644 --- a/jenkins/6-forecast.md +++ b/jenkins/3-forecast.md @@ -101,4 +101,4 @@ You can now inspect the output of the command to see a forecast report using all ## Next steps -This concludes all labs for migrating Jenkins pipelines to Actions with Valet! +[Perform a dry-run migration of a Jenkins pipeline](4-dry-run.md) diff --git a/jenkins/3-dry-run.md b/jenkins/4-dry-run.md similarity index 98% rename from jenkins/3-dry-run.md rename to jenkins/4-dry-run.md index 19f5145..e0cd0d8 100644 --- a/jenkins/3-dry-run.md +++ b/jenkins/4-dry-run.md @@ -141,4 +141,4 @@ Try running the `dry-run` command for different pipelines in the Jenkins server. ## Next lab -[Use custom transformers to customize Valet's behavior](4-custom-transformers.md) +[Use custom transformers to customize Valet's behavior](5-custom-transformers.md) diff --git a/jenkins/4-custom-transformers.md b/jenkins/5-custom-transformers.md similarity index 99% rename from jenkins/4-custom-transformers.md rename to jenkins/5-custom-transformers.md index e345308..129509f 100644 --- a/jenkins/4-custom-transformers.md +++ b/jenkins/5-custom-transformers.md @@ -290,4 +290,4 @@ That's it! Congratulations, you have overridden Valet's default behavior by cust ## Next lab -[Perform a production migration of a Jenkins pipeline](5-migrate.md) +[Perform a production migration of a Jenkins pipeline](6-migrate.md) diff --git a/jenkins/5-migrate.md b/jenkins/6-migrate.md similarity index 97% rename from jenkins/5-migrate.md rename to jenkins/6-migrate.md index 66a8f11..325a620 100644 --- a/jenkins/5-migrate.md +++ b/jenkins/6-migrate.md @@ -52,4 +52,4 @@ At this point, the migration has completed and you have successfully migrated a ### Next lab -[Forecast potential build runner usage](6-forecast.md) +This concludes all labs for migrating Jenkins pipelines to Actions with Valet!