From 2ae5b183f6489bfccc6730fb62a8d9f976d30e8f Mon Sep 17 00:00:00 2001 From: Ethan Dennis Date: Wed, 14 Sep 2022 11:28:36 -0700 Subject: [PATCH] reorder azdo labs --- azure_devops/2-audit.md | 2 +- azure_devops/{6-forecast.md => 3-forecast.md} | 2 +- azure_devops/{3-dry-run.md => 4-dry-run.md} | 2 +- .../{4-custom-transformers.md => 5-custom-transformers.md} | 2 +- azure_devops/{5-migrate.md => 6-migrate.md} | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) rename azure_devops/{6-forecast.md => 3-forecast.md} (98%) rename azure_devops/{3-dry-run.md => 4-dry-run.md} (97%) rename azure_devops/{4-custom-transformers.md => 5-custom-transformers.md} (99%) rename azure_devops/{5-migrate.md => 6-migrate.md} (97%) diff --git a/azure_devops/2-audit.md b/azure_devops/2-audit.md index fd1147a..d9d58f9 100644 --- a/azure_devops/2-audit.md +++ b/azure_devops/2-audit.md @@ -172,4 +172,4 @@ Each pipeline will have a variety of files written that include: ### Next lab -[Perform a dry-run migration of an Azure DevOps pipeline](3-dry-run.md) +[Forecast potential build runner usage](3-forecast.md) diff --git a/azure_devops/6-forecast.md b/azure_devops/3-forecast.md similarity index 98% rename from azure_devops/6-forecast.md rename to azure_devops/3-forecast.md index 48e6d84..cb188a9 100644 --- a/azure_devops/6-forecast.md +++ b/azure_devops/3-forecast.md @@ -101,4 +101,4 @@ Additionally, these metrics are defined for each queue of runners defined in Azu ## Next steps -This concludes all labs for migrating Azure DevOps pipelines to Actions with Valet! +[Perform a dry-run migration of an Azure DevOps pipeline](4-dry-run.md) diff --git a/azure_devops/3-dry-run.md b/azure_devops/4-dry-run.md similarity index 97% rename from azure_devops/3-dry-run.md rename to azure_devops/4-dry-run.md index ac60718..dc15aac 100644 --- a/azure_devops/3-dry-run.md +++ b/azure_devops/4-dry-run.md @@ -90,4 +90,4 @@ Despite these two pipelines using different syntax they will function equivalent ## 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/azure_devops/4-custom-transformers.md b/azure_devops/5-custom-transformers.md similarity index 99% rename from azure_devops/4-custom-transformers.md rename to azure_devops/5-custom-transformers.md index cec9e8a..c46a28b 100644 --- a/azure_devops/4-custom-transformers.md +++ b/azure_devops/5-custom-transformers.md @@ -232,4 +232,4 @@ That's it! At this point you have overridden Valet's default behavior by customi ## Next lab -[Perform a production migration of an Azure DevOps pipeline](5-migrate.md) +[Perform a production migration of an Azure DevOps pipeline](6-migrate.md) diff --git a/azure_devops/5-migrate.md b/azure_devops/6-migrate.md similarity index 97% rename from azure_devops/5-migrate.md rename to azure_devops/6-migrate.md index 43e17a1..f735447 100644 --- a/azure_devops/5-migrate.md +++ b/azure_devops/6-migrate.md @@ -57,4 +57,4 @@ At this point, the migration has completed and you have successfully migrated an ### Next lab -[Forecast potential build runner usage](6-forecast.md) +This concludes all labs for migrating Azure DevOps pipelines to Actions with Valet!