From c561fbd9daa3dbbb6ab2c7ff3bd4478a893c80d3 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Wed, 31 Aug 2022 10:48:59 -0400 Subject: [PATCH] Update valet-forecast-lab.md --- azure_devops/valet-forecast-lab.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/azure_devops/valet-forecast-lab.md b/azure_devops/valet-forecast-lab.md index 4220e24..c969f76 100644 --- a/azure_devops/valet-forecast-lab.md +++ b/azure_devops/valet-forecast-lab.md @@ -5,7 +5,6 @@ In this lab we will use the `forecast` command to forecast potential GitHub Acti - [Prepare for forecast](#prepare-for-forecast) - [Perform a forecast](#perform-a-forecast) - [Review forecast report](#review-forecast-report) -- [Forecasting multiple providers](#forecasting-multiple-providers) - [Next steps](#next-steps) ## Prerequisites @@ -177,9 +176,7 @@ Open the forecast report and review the calculated metrics. - Max: **4** ### Runner Group Sections -- The preceding sections shows the same metrics as the `Total` section, but are broken out into runner groups. A runner group is a logical grouping of one or more runners. - - -## Forecasting multiple providers +- The preceding sections shows the same metrics as the `Total` section, but are broken out into runner groups. A runner group is a logical grouping of one or more runners. In our case we have `Azure Pipelines` and `Default`. These sections can be used to identify runner types that needed to be increased or decreased when moving to GitHub Actions. Looking at the report the `Default` group was only used for 3 jobs and a ran for a total of 1 minute. This might be a group of runners we do not need to migrate to Actions. ## Next steps +This concludes the Valet labs for Azure Devops, if you are interested exploring the power of Valet more. You can leverage the lab setup and modify and add new pipelines that more closely match your needs and try out the commands again!