Remove jenkins refs in gitlab

This commit is contained in:
Ethan Dennis
2022-09-06 17:14:44 -07:00
parent fa6f0e56ee
commit 21d697b5e3
4 changed files with 6 additions and 6 deletions
+2 -2
View File
@@ -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
+1 -1
View File
@@ -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__
+2 -2
View File
@@ -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.
+1 -1
View File
@@ -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!