From 21d697b5e3ba62f2405f3c66aabecf936ad3eada Mon Sep 17 00:00:00 2001 From: Ethan Dennis Date: Tue, 6 Sep 2022 17:14:44 -0700 Subject: [PATCH] Remove jenkins refs in gitlab --- gitlab/2-audit.md | 4 ++-- gitlab/3-dry-run.md | 2 +- gitlab/4-custom-transformers.md | 4 ++-- gitlab/6-forecast.md | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/gitlab/2-audit.md b/gitlab/2-audit.md index 4c5d7e2..09c1cac 100644 --- a/gitlab/2-audit.md +++ b/gitlab/2-audit.md @@ -6,7 +6,7 @@ The `audit` command operates by fetching all of the pipelines defined in a GitLa ## Prerequisites -1. Followed the steps [here](./readme.md#configure-your-codespace) to set up your Codespace environment and start a Jenkins server. +1. Followed the steps [here](./readme.md#configure-your-codespace) to set up your Codespace environment and start a GitLab server. 2. Completed the [configure lab](./1-configure.md#configuring-credentials). ## Perform an audit @@ -172,7 +172,7 @@ The final section of the audit report provides a manifest of all of the files th Each pipeline will have a variety of files written that include: -- The original pipeline as it was defined in Jenkins. +- The original pipeline as it was defined in GitLab. - Any network responses used to convert a pipeline. - The converted workflow. - Stack traces that can used to troubleshoot a failed pipeline conversion diff --git a/gitlab/3-dry-run.md b/gitlab/3-dry-run.md index fbb8c46..cf66935 100644 --- a/gitlab/3-dry-run.md +++ b/gitlab/3-dry-run.md @@ -10,7 +10,7 @@ In this lab you will use the `dry-run` command to convert a GitLab pipeline to i ## Perform a dry run -We will be performing a dry-run against a pipeline in your preconfigured Jenkins server. We will need to answer the following questions before running this command: +We will be performing a dry-run against a pipeline in your preconfigured GitLab server. We will need to answer the following questions before running this command: 1. What is the project we want to convert? - __basic-pipeline-example__ diff --git a/gitlab/4-custom-transformers.md b/gitlab/4-custom-transformers.md index 72184c6..92898d1 100644 --- a/gitlab/4-custom-transformers.md +++ b/gitlab/4-custom-transformers.md @@ -18,7 +18,7 @@ In this lab we will build upon the `dry-run` command to override Valet's default We will be performing a `dry-run` command to inspect the workflow that is converted by default. Run the following command within the codespace terminal: ```bash -gh valet dry-run jenkins gitlab --output-dir tmp --namespace valet --project terraform-example +gh valet dry-run gitlab --output-dir tmp --namespace valet --project terraform-example ``` The converted workflow that is generated by the above command can be seen below: @@ -95,7 +95,7 @@ This method can use any valid ruby syntax and should return a `Hash` that repres Now, we can perform another `dry-run` command and use the `--custom-transformers` CLI option to provide this custom transformer. Run the following command within your codespace terminal: ```bash -gh valet dry-run jenkins gitlab --output-dir tmp --namespace valet --project terraform-example --custom-transformers transformers.rb +gh valet dry-run gitlab --output-dir tmp --namespace valet --project terraform-example --custom-transformers transformers.rb ``` The converted workflow that is generated by the above command will now use the custom logic for the `artifacts.terraform` step. diff --git a/gitlab/6-forecast.md b/gitlab/6-forecast.md index d94a68a..6d78f38 100644 --- a/gitlab/6-forecast.md +++ b/gitlab/6-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! +This concludes all labs for migrating GitLab pipelines to Actions with Valet!