From 143fac003d488976c6cb5d2dab6bdb43f8f9caa6 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Wed, 17 Aug 2022 13:29:05 -0400 Subject: [PATCH] Update valet-forecast-lab.md --- gitlab/valet-forecast-lab.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/gitlab/valet-forecast-lab.md b/gitlab/valet-forecast-lab.md index 9f4d59c..f605cb2 100644 --- a/gitlab/valet-forecast-lab.md +++ b/gitlab/valet-forecast-lab.md @@ -1,7 +1,8 @@ # Forecast the usage of a GitLab namespace -## TBD +In this lab we will us the `forecast` command to forecast potential GitHub Actions usage by computing metrics from historical pipeline data in the GitLab instance. The metrics will be stored on disk in a markdown file and include job metrics for execution time, queue time, and concurrency. We will look at each of these metrics in this lab. - [Prerequisites](#prerequisites) +- [Prepare for forecast](#prepare-for-forecast) - [Perform a forecast](#perform-a-forecast) - [Review forecast output](#review-forecast-output) @@ -10,6 +11,10 @@ 1. Followed [steps](../gitlab#readme) to set up your codespace environment. 2. Completed the [configure lab](../gitlab/valet-configure-lab.md) +## Prepare for forecast +Before we can run the forecast we need to answer a few questions so we can construct the correct command +1) What namespace do we want to run the forecast for? __Valet__. +2) What timeframe do we want to forecast? ## Perform a forecast ### TBD