From 3a1d8fcea9dca481ca65280859a2cfc3a54306d1 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Wed, 10 Aug 2022 15:44:44 -0400 Subject: [PATCH 01/10] Create valet-dry-run-lab.md --- gitlab/valet-dry-run-lab.md | 42 +++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 gitlab/valet-dry-run-lab.md diff --git a/gitlab/valet-dry-run-lab.md b/gitlab/valet-dry-run-lab.md new file mode 100644 index 0000000..a451323 --- /dev/null +++ b/gitlab/valet-dry-run-lab.md @@ -0,0 +1,42 @@ +# Dry run the migration of an GitLab pipeline to GitHub Actions +In this lab, you will use the Valet `dry-run` command to convert a GitLab pipeline to it's equivalent GitHub Actions workflow. +The end result of this command will the actions workflow writen to your local filesystem. + +- [Prerequisites](#prerequisites) +- [Perform a dry run](#perform-a-dry-run) +- [View dry-run output](#view-dry-run-output) +- [Next Lab](#next-lab) + +## Prerequisites + +1. Followed [steps](../gitlab#readme) to set up your codespace environment. +2. Completed the configure [lab](../gitlab/valet-configure-lab.md) + + +## Perform a dry run +We will be performing a dry-run against a preconfigured project in the GitLab instance. Before running the command we need to collect some information: + 1. What is the project we want to convert? basic-pipeline-example + 2. What is the namespace for that project? Valet. In this case the namespace is the same as the group the project is in. + 3. Where do we want to store the result? ./tmp/dry-run-lab. This can be any valid path on the system. In the case of codespaces it is generally best to use `./tmp/SOME_DIRECTORY_HERE` so they files show in explorer + +#### Steps +1. Navigate to the codespace terminal +2. Run the dry-run command + ``` + gh valet dry-run gitlab --output-dir ./tmp/dry-run-lab --namespace valet --project basic-pipeline-example` + ``` +3. Valet should have printed the output files in the terminal. +4. Navigate to `./tmp/dry-run-lab` in the Explorer pane in codespaces and open `basic-pipeline-example.yml`. This is the converted GitHub Actions YAML file. +### Example +ADD_IMAGE + +## View dry-run output +The dry-run output will show you the GitHub Actions yaml that will be migrated to GitHub. + +### Example +ADD_IMAGE + +### Next Lab +TBD + + From fc38662ee23aa0caef697faff33462df2ff07b87 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Thu, 11 Aug 2022 11:59:44 -0400 Subject: [PATCH 02/10] Update valet-dry-run-lab.md --- gitlab/valet-dry-run-lab.md | 25 ++++++++++++++----------- 1 file changed, 14 insertions(+), 11 deletions(-) diff --git a/gitlab/valet-dry-run-lab.md b/gitlab/valet-dry-run-lab.md index a451323..271de84 100644 --- a/gitlab/valet-dry-run-lab.md +++ b/gitlab/valet-dry-run-lab.md @@ -1,6 +1,6 @@ # Dry run the migration of an GitLab pipeline to GitHub Actions In this lab, you will use the Valet `dry-run` command to convert a GitLab pipeline to it's equivalent GitHub Actions workflow. -The end result of this command will the actions workflow writen to your local filesystem. +The end result of this command will be the actions workflow writen to your local filesystem. - [Prerequisites](#prerequisites) - [Perform a dry run](#perform-a-dry-run) @@ -10,25 +10,28 @@ The end result of this command will the actions workflow writen to your local fi ## Prerequisites 1. Followed [steps](../gitlab#readme) to set up your codespace environment. -2. Completed the configure [lab](../gitlab/valet-configure-lab.md) +2. Completed the [configure lab](../gitlab/valet-configure-lab.md) ## Perform a dry run We will be performing a dry-run against a preconfigured project in the GitLab instance. Before running the command we need to collect some information: - 1. What is the project we want to convert? basic-pipeline-example - 2. What is the namespace for that project? Valet. In this case the namespace is the same as the group the project is in. - 3. Where do we want to store the result? ./tmp/dry-run-lab. This can be any valid path on the system. In the case of codespaces it is generally best to use `./tmp/SOME_DIRECTORY_HERE` so they files show in explorer + 1. What is the project we want to convert? __basic-pipeline-example__ + 2. What is the namespace for that project? __Valet. In this case the namespace is the same as the group the project is in__ + 3. Where do we want to store the result? __./tmp/dry-run-lab. This can be any valid path on the system. In the case of codespaces it is generally best to use `./tmp/SOME_DIRECTORY_HERE` so the files show in explorer__ #### Steps 1. Navigate to the codespace terminal -2. Run the dry-run command +2. Run the dry-run command using the values determined above ``` - gh valet dry-run gitlab --output-dir ./tmp/dry-run-lab --namespace valet --project basic-pipeline-example` + gh valet dry-run gitlab --output-dir ./tmp/dry-run-lab --namespace valet --project basic-pipeline-example ``` -3. Valet should have printed the output files in the terminal. -4. Navigate to `./tmp/dry-run-lab` in the Explorer pane in codespaces and open `basic-pipeline-example.yml`. This is the converted GitHub Actions YAML file. -### Example -ADD_IMAGE +3. When the command finishes the output files should be printed to the terminal. + dry-run-terminal +4. Open generated actions workflow + - Find `./tmp/dry-run-lab/valet` in the file explorer pane in codespaces. + - Click `basic-pipeline-example.yml` to opendr + dry-run-explorer + ## View dry-run output The dry-run output will show you the GitHub Actions yaml that will be migrated to GitHub. From 8d3401a6614aff8bb19868a74d1ac9cf367c2a5c Mon Sep 17 00:00:00 2001 From: j-dunham Date: Thu, 11 Aug 2022 12:59:14 -0400 Subject: [PATCH 03/10] Update valet-dry-run-lab.md --- gitlab/valet-dry-run-lab.md | 115 +++++++++++++++++++++++++++++++++++- 1 file changed, 113 insertions(+), 2 deletions(-) diff --git a/gitlab/valet-dry-run-lab.md b/gitlab/valet-dry-run-lab.md index 271de84..a8176a5 100644 --- a/gitlab/valet-dry-run-lab.md +++ b/gitlab/valet-dry-run-lab.md @@ -33,8 +33,119 @@ We will be performing a dry-run against a preconfigured project in the GitLab in dry-run-explorer -## View dry-run output -The dry-run output will show you the GitHub Actions yaml that will be migrated to GitHub. +## Review dry-run output +The dry-run output will show you the GitHub Actions yaml that would be migrated to GitHub with the `migrate` command. We will now take a quick look at what was generated + +In the GitLab pipeline we had 3 stages and 6 jobs. +
+ GitLab Pipeline +```yaml + # Testing +``` +
+ +In the resulting yaml we have the same +
+Actions Workflow + +```yaml +name: valet/basic-pipeline-example +on: + push: + workflow_dispatch: +concurrency: + group: "${{ github.ref }}" + cancel-in-progress: true +jobs: + build_a: + runs-on: ubuntu-latest + container: + image: alpine + timeout-minutes: 60 + steps: + - uses: actions/checkout@v2 + with: + fetch-depth: 20 + lfs: true + - run: echo "This job builds something." + - run: sleep 100 + build_b: + runs-on: ubuntu-latest + container: + image: alpine + timeout-minutes: 60 + steps: + - uses: actions/checkout@v2 + with: + fetch-depth: 20 + lfs: true + - run: echo "This job builds something else." + - run: sleep 70 + test_a: + needs: + - build_a + - build_b + runs-on: ubuntu-latest + container: + image: alpine + timeout-minutes: 60 + steps: + - uses: actions/checkout@v2 + with: + fetch-depth: 20 + lfs: true + - run: echo "This job tests something. It will only run when all jobs in the" + - run: echo "build stage are complete." + test_b: + needs: + - build_a + - build_b + runs-on: ubuntu-latest + container: + image: alpine + timeout-minutes: 60 + steps: + - uses: actions/checkout@v2 + with: + fetch-depth: 20 + lfs: true + - run: echo "This job tests something else. It will only run when all jobs in the" + - run: echo "build stage are complete too. It will start at about the same time as test_a." + - run: sleep 300 + deploy_a: + needs: + - test_a + - test_b + runs-on: ubuntu-latest + container: + image: alpine + timeout-minutes: 60 + steps: + - uses: actions/checkout@v2 + with: + fetch-depth: 20 + lfs: true + - run: echo "This job deploys something. It will only run when all jobs in the" + - run: echo "test stage complete." + - run: sleep 600 + deploy_b: + needs: + - test_a + - test_b + runs-on: ubuntu-latest + container: + image: alpine + timeout-minutes: 60 + steps: + - uses: actions/checkout@v2 + with: + fetch-depth: 20 + lfs: true + - run: echo "This job deploys something else. It will only run when all jobs in the" + - run: echo "test stage complete. It will start at about the same time as deploy_a." + - run: sleep 400 +``` +
### Example ADD_IMAGE From 12f26b27e27993b6da0c15db9c1f50520697bb89 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Thu, 11 Aug 2022 15:23:15 -0400 Subject: [PATCH 04/10] Update valet-dry-run-lab.md --- gitlab/valet-dry-run-lab.md | 87 ++++++++++++++++++++++++++++++++----- 1 file changed, 77 insertions(+), 10 deletions(-) diff --git a/gitlab/valet-dry-run-lab.md b/gitlab/valet-dry-run-lab.md index a8176a5..ae9670b 100644 --- a/gitlab/valet-dry-run-lab.md +++ b/gitlab/valet-dry-run-lab.md @@ -4,7 +4,7 @@ The end result of this command will be the actions workflow writen to your local - [Prerequisites](#prerequisites) - [Perform a dry run](#perform-a-dry-run) -- [View dry-run output](#view-dry-run-output) +- [Review dry-run output](#review-dry-run-output) - [Next Lab](#next-lab) ## Prerequisites @@ -34,19 +34,86 @@ We will be performing a dry-run against a preconfigured project in the GitLab in ## Review dry-run output -The dry-run output will show you the GitHub Actions yaml that would be migrated to GitHub with the `migrate` command. We will now take a quick look at what was generated +The dry-run output will show you the GitHub Actions yaml that would be migrated to GitHub with the `migrate` command. We will now take a quick look at what was generated. -In the GitLab pipeline we had 3 stages and 6 jobs. +In the GitLab pipeline we had 3 stages and 6 jobs that run on a alpine image
- GitLab Pipeline + Click to expand GitLab Pipeline + ```yaml - # Testing +stages: + - build + - test + - deploy + +image: alpine + +build_a: + stage: build + script: + - echo "This job builds something." + - sleep 100 + +build_b: + stage: build + script: + - echo "This job builds something else." + - sleep 70 + +test_a: + stage: test + script: + - echo "This job tests something. It will only run when all jobs in the" + - echo "build stage are complete." + +test_b: + stage: test + script: + - echo "This job tests something else. It will only run when all jobs in the" + - echo "build stage are complete too. It will start at about the same time as test_a." + - sleep 300 + +deploy_a: + stage: deploy + script: + - echo "This job deploys something. It will only run when all jobs in the" + - echo "test stage complete." + - sleep 600 + +deploy_b: + stage: deploy + script: + - echo "This job deploys something else. It will only run when all jobs in the" + - echo "test stage complete. It will start at about the same time as deploy_a." + - sleep 400 + ``` +
-In the resulting yaml we have the same +In the resulting yaml we have the same jobs (`build_a`, `build_b`, `test_a`, `test_b`, `deploy_a`, `deploy_b`) and the stages are now being enforced using Actions's keyword `needs`. We can see this if we examine the `needs` for test_a and test_b, which make the test jobs depend on the build jobs. +```diff +- stages: test ++ needs: ++ - build_a ++ - build_b +``` + +The `image` in the GitLab pipeline has be transformed to `container` on each of the jobs. +```diff +- image: alpine ++ container: ++ image: alpine +``` +And `script` has been transformed to `run` +```diff +- script: +- - echo "This job builds something." ++ run: echo "This job builds something." +``` +
-Actions Workflow + Click to expand Actions Workflow ```yaml name: valet/basic-pipeline-example @@ -147,10 +214,10 @@ jobs: ```
-### Example -ADD_IMAGE +## Includes Dry-Run +In the previous dry-run we migrated a basic pipeline that map very nicely to concepts in GitHub Actions. In this section we will dry-run a pipeline that does not map directly to Actions. The `include-file-example` pipeline -### Next Lab +## Next Lab TBD From 422b4550e89a63830cee61d87e8f0f71db308cc6 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Thu, 11 Aug 2022 15:30:06 -0400 Subject: [PATCH 05/10] Update valet-dry-run-lab.md --- gitlab/valet-dry-run-lab.md | 50 +++++++++++++++++++------------------ 1 file changed, 26 insertions(+), 24 deletions(-) diff --git a/gitlab/valet-dry-run-lab.md b/gitlab/valet-dry-run-lab.md index ae9670b..cc9e99a 100644 --- a/gitlab/valet-dry-run-lab.md +++ b/gitlab/valet-dry-run-lab.md @@ -36,9 +36,9 @@ We will be performing a dry-run against a preconfigured project in the GitLab in ## Review dry-run output The dry-run output will show you the GitHub Actions yaml that would be migrated to GitHub with the `migrate` command. We will now take a quick look at what was generated. -In the GitLab pipeline we had 3 stages and 6 jobs that run on a alpine image +__Click to Expand__
- Click to expand GitLab Pipeline + GitLab Pipeline ```yaml stages: @@ -91,29 +91,8 @@ deploy_b:
-In the resulting yaml we have the same jobs (`build_a`, `build_b`, `test_a`, `test_b`, `deploy_a`, `deploy_b`) and the stages are now being enforced using Actions's keyword `needs`. We can see this if we examine the `needs` for test_a and test_b, which make the test jobs depend on the build jobs. -```diff -- stages: test -+ needs: -+ - build_a -+ - build_b -``` - -The `image` in the GitLab pipeline has be transformed to `container` on each of the jobs. -```diff -- image: alpine -+ container: -+ image: alpine -``` -And `script` has been transformed to `run` -```diff -- script: -- - echo "This job builds something." -+ run: echo "This job builds something." -``` -
- Click to expand Actions Workflow + Actions Workflow ```yaml name: valet/basic-pipeline-example @@ -214,6 +193,29 @@ jobs: ```
+In the GitLab pipeline we had 3 stages and 6 jobs that run on a alpine image + +In the Actions workflow we have the same jobs (`build_a`, `build_b`, `test_a`, `test_b`, `deploy_a`, `deploy_b`) and the stages are now being enforced using the `needs` keyword. We can see this if we examine the `needs` for `test_a` and `test_b`, which make the test jobs depend on the build jobs. +```diff +- stages: test ++ needs: ++ - build_a ++ - build_b +``` + +The `image` in the GitLab pipeline has be transformed to `container` on each of the jobs. +```diff +- image: alpine ++ container: ++ image: alpine +``` +And `script` has been transformed to `run` +```diff +- script: +- - echo "This job builds something." ++ run: echo "This job builds something." +``` + ## Includes Dry-Run In the previous dry-run we migrated a basic pipeline that map very nicely to concepts in GitHub Actions. In this section we will dry-run a pipeline that does not map directly to Actions. The `include-file-example` pipeline From 4d309eea57ac3f3059e7e9a50bda942433a0ed59 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Thu, 11 Aug 2022 15:58:29 -0400 Subject: [PATCH 06/10] Update valet-dry-run-lab.md --- gitlab/valet-dry-run-lab.md | 48 +++++++++++++++++++++++++++++++++---- 1 file changed, 43 insertions(+), 5 deletions(-) diff --git a/gitlab/valet-dry-run-lab.md b/gitlab/valet-dry-run-lab.md index cc9e99a..dd8fdf1 100644 --- a/gitlab/valet-dry-run-lab.md +++ b/gitlab/valet-dry-run-lab.md @@ -1,6 +1,6 @@ # Dry run the migration of an GitLab pipeline to GitHub Actions -In this lab, you will use the Valet `dry-run` command to convert a GitLab pipeline to it's equivalent GitHub Actions workflow. -The end result of this command will be the actions workflow writen to your local filesystem. +In this lab, you will use the Valet `dry-run` command to convert a GitLab pipeline to its equivalent GitHub Actions workflow. +The end result of this command will be the actions workflow written to your local filesystem. - [Prerequisites](#prerequisites) - [Perform a dry run](#perform-a-dry-run) @@ -29,7 +29,7 @@ We will be performing a dry-run against a preconfigured project in the GitLab in dry-run-terminal 4. Open generated actions workflow - Find `./tmp/dry-run-lab/valet` in the file explorer pane in codespaces. - - Click `basic-pipeline-example.yml` to opendr + - Click `basic-pipeline-example.yml` to open dry-run-explorer @@ -217,9 +217,47 @@ And `script` has been transformed to `run` ``` ## Includes Dry-Run -In the previous dry-run we migrated a basic pipeline that map very nicely to concepts in GitHub Actions. In this section we will dry-run a pipeline that does not map directly to Actions. The `include-file-example` pipeline +In the previous dry-run we migrated a basic pipeline that map very nicely to concepts in GitHub Actions. In this section we will dry-run a pipeline that does not map directly to Actions. The `included-files-example` pipeline which looks like +```yaml +include: + - local: /config/build.gitlab-ci.yml + - local: /config/test.gitlab-ci.yml +``` +which results in the below yaml. The difference to note here is that Valet transformed the pipeline into a single workflow, it did not create reusable workflows for the `include` files `/config/build.gitlab-ci.yml` and `/config/test.gitlab-ci.yml`. The reason for this is that the dependance graph of how the jobs run could not be guaranteed using reusable workflows. This is an example of how concepts in GitLab don't always map directly to Actions and Valet has to make a decision on the safest path to transform a pipeline. It is likely this could be refactored to use [reusable workflow](https://docs.github.com/en/actions/using-workflows/reusing-workflows) at a later date. +```yaml +name: valet/included-files-example +on: + push: + pull_request: + workflow_dispatch: +concurrency: + group: "${{ github.ref }}" + cancel-in-progress: true +jobs: + build: + runs-on: ubuntu-latest + timeout-minutes: 60 + steps: + - uses: actions/checkout@v2 + with: + fetch-depth: 50 + lfs: true + - run: echo "[BEFORE_SCRIPT] this is from test.gitlab-ci.yml" + - run: echo "this is from a local file" + test: + needs: build + runs-on: ubuntu-latest + timeout-minutes: 60 + steps: + - uses: actions/checkout@v2 + with: + fetch-depth: 50 + lfs: true + - run: echo "[BEFORE_SCRIPT] this is from test.gitlab-ci.yml" + - run: echo "this is from a local file" +``` ## Next Lab -TBD +[Audit GitLab Pipelines to GitHub Actions](../gitlab/valet-audit-lab.md) From d8ea3d1902355fd3d73aa515fa836afef01887c8 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Thu, 11 Aug 2022 16:08:25 -0400 Subject: [PATCH 07/10] Update valet-dry-run-lab.md --- gitlab/valet-dry-run-lab.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/gitlab/valet-dry-run-lab.md b/gitlab/valet-dry-run-lab.md index dd8fdf1..7bf5a05 100644 --- a/gitlab/valet-dry-run-lab.md +++ b/gitlab/valet-dry-run-lab.md @@ -5,6 +5,7 @@ The end result of this command will be the actions workflow written to your loca - [Prerequisites](#prerequisites) - [Perform a dry run](#perform-a-dry-run) - [Review dry-run output](#review-dry-run-output) +- [Includes Dry-Run](#includes-dry-run) - [Next Lab](#next-lab) ## Prerequisites @@ -217,13 +218,13 @@ And `script` has been transformed to `run` ``` ## Includes Dry-Run -In the previous dry-run we migrated a basic pipeline that map very nicely to concepts in GitHub Actions. In this section we will dry-run a pipeline that does not map directly to Actions. The `included-files-example` pipeline which looks like +In the previous dry-run we migrated a basic pipeline that map very nicely to concepts in GitHub Actions. In this section we will examine the results of a dry-run that does not map directly to Actions using the `included-files-example` pipeline, which looks like ```yaml include: - local: /config/build.gitlab-ci.yml - local: /config/test.gitlab-ci.yml ``` -which results in the below yaml. The difference to note here is that Valet transformed the pipeline into a single workflow, it did not create reusable workflows for the `include` files `/config/build.gitlab-ci.yml` and `/config/test.gitlab-ci.yml`. The reason for this is that the dependance graph of how the jobs run could not be guaranteed using reusable workflows. This is an example of how concepts in GitLab don't always map directly to Actions and Valet has to make a decision on the safest path to transform a pipeline. It is likely this could be refactored to use [reusable workflow](https://docs.github.com/en/actions/using-workflows/reusing-workflows) at a later date. +and results in the below yaml. The difference to note here is that Valet transformed the pipeline into a single workflow, it did not create reusable workflows for the `include` files `/config/build.gitlab-ci.yml` and `/config/test.gitlab-ci.yml`. The reason for this is that the dependency graph of how the jobs run could not be guaranteed using reusable workflows. This is an example of how concepts in GitLab don't always map directly to Actions and Valet has to make a decision on the safest path forward. It is likely this could be refactored to use [reusable workflow](https://docs.github.com/en/actions/using-workflows/reusing-workflows) at a later date with a deeper understanding of pipeline. ```yaml name: valet/included-files-example on: @@ -257,6 +258,8 @@ jobs: - run: echo "this is from a local file" ``` +Try constructing and running the `dry-run` command yourself. Hint, you should just have to change the project name. + ## Next Lab [Audit GitLab Pipelines to GitHub Actions](../gitlab/valet-audit-lab.md) From dbff6a68c2a37064008ea05eb29d59702d0eeaf8 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Thu, 11 Aug 2022 16:09:46 -0400 Subject: [PATCH 08/10] Update valet-dry-run-lab.md --- gitlab/valet-dry-run-lab.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gitlab/valet-dry-run-lab.md b/gitlab/valet-dry-run-lab.md index 7bf5a05..7b6e223 100644 --- a/gitlab/valet-dry-run-lab.md +++ b/gitlab/valet-dry-run-lab.md @@ -224,7 +224,7 @@ include: - local: /config/build.gitlab-ci.yml - local: /config/test.gitlab-ci.yml ``` -and results in the below yaml. The difference to note here is that Valet transformed the pipeline into a single workflow, it did not create reusable workflows for the `include` files `/config/build.gitlab-ci.yml` and `/config/test.gitlab-ci.yml`. The reason for this is that the dependency graph of how the jobs run could not be guaranteed using reusable workflows. This is an example of how concepts in GitLab don't always map directly to Actions and Valet has to make a decision on the safest path forward. It is likely this could be refactored to use [reusable workflow](https://docs.github.com/en/actions/using-workflows/reusing-workflows) at a later date with a deeper understanding of pipeline. +and results in the below yaml. The difference to note here is that Valet transformed the pipeline into a single workflow, it did not create reusable workflows for the `include` files `/config/build.gitlab-ci.yml` and `/config/test.gitlab-ci.yml`. The reason for this is that the dependency graph of how the jobs run could not be guaranteed using reusable workflows. This is an example of how concepts in GitLab don't always map directly to Actions and Valet has to make a decision on the safest path forward. It is likely this could be refactored to use [reusable workflow](https://docs.github.com/en/actions/using-workflows/reusing-workflows) at a later date with a deeper understanding of the pipeline. ```yaml name: valet/included-files-example on: From e633cd12825d0a6e751d8c868758045cc7160e0b Mon Sep 17 00:00:00 2001 From: j-dunham Date: Thu, 11 Aug 2022 20:45:52 -0400 Subject: [PATCH 09/10] Update gitlab/valet-dry-run-lab.md Co-authored-by: Begona Guereca --- gitlab/valet-dry-run-lab.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gitlab/valet-dry-run-lab.md b/gitlab/valet-dry-run-lab.md index 7b6e223..24f5058 100644 --- a/gitlab/valet-dry-run-lab.md +++ b/gitlab/valet-dry-run-lab.md @@ -218,7 +218,7 @@ And `script` has been transformed to `run` ``` ## Includes Dry-Run -In the previous dry-run we migrated a basic pipeline that map very nicely to concepts in GitHub Actions. In this section we will examine the results of a dry-run that does not map directly to Actions using the `included-files-example` pipeline, which looks like +In the previous dry-run we migrated a basic pipeline that mapped very nicely to concepts in GitHub Actions. In this section we will examine the results of a dry-run that does not map directly to Actions using the `included-files-example` pipeline, which looks like ```yaml include: - local: /config/build.gitlab-ci.yml From 9056585b78485cccc7215703a5c0416d832b3c23 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Thu, 11 Aug 2022 20:46:14 -0400 Subject: [PATCH 10/10] Update gitlab/valet-dry-run-lab.md Co-authored-by: Begona Guereca --- gitlab/valet-dry-run-lab.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gitlab/valet-dry-run-lab.md b/gitlab/valet-dry-run-lab.md index 24f5058..9c743c0 100644 --- a/gitlab/valet-dry-run-lab.md +++ b/gitlab/valet-dry-run-lab.md @@ -20,7 +20,7 @@ We will be performing a dry-run against a preconfigured project in the GitLab in 2. What is the namespace for that project? __Valet. In this case the namespace is the same as the group the project is in__ 3. Where do we want to store the result? __./tmp/dry-run-lab. This can be any valid path on the system. In the case of codespaces it is generally best to use `./tmp/SOME_DIRECTORY_HERE` so the files show in explorer__ -#### Steps +### Steps 1. Navigate to the codespace terminal 2. Run the dry-run command using the values determined above ```