actions/importer-labs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Readme edits

Browse Source
This commit is contained in:
Jennifer Kerns
2022-09-13 08:55:51 -04:00
committed by GitHub
parent 15d5df048d
commit a3f2fe338f
22 changed files with 287 additions and 287 deletions
Download Patch File Download Diff File Expand all files Collapse all files
gitlab/3-dry-run.md
+11 -11
View File
@@ -1,4 +1,4 @@
# Perform a dry-run of a GitLab pipeline
# Perform a dry-run migration of a GitLab pipeline
In this lab you will use the `dry-run` command to convert a GitLab pipeline to its equivalent GitHub Actions workflow.
@@ -10,20 +10,20 @@ 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 GitLab server. We will need to answer the following questions before running this command:
You will be performing a dry run against a pipeline in your preconfigured GitLab server. Answer the following questions before running this command:
1. What is the project we want to convert?
1. What project do you want to convert?
- __basic-pipeline-example__
2. What is the namespace for that project?
- __Valet__
3. Where do we want to store the result?
- __./tmp/dry-run-lab__. This can be any path within the working directory that Valet commands are executed from.
3. Where do you want to store the result?
- __./tmp/dry-run-lab__. This can be any path within the working directory from which Valet commands are executed.
### Steps
1. Navigate to the codespace terminal
1. Navigate to your codespace terminal
2. Run the following command from the root directory:
```bash
@@ -35,7 +35,7 @@ We will be performing a dry-run against a pipeline in your preconfigured GitLab
![img](https://user-images.githubusercontent.com/18723510/184173635-aec28d1c-8c61-4dcf-a743-f86cbdc836c5.png)
4. View the converted workflow:
- Find `./tmp/dry-run/valet` in the file explorer pane in codespaces.
- Find `./tmp/dry-run/valet` in the file explorer pane in your codespace.
- Click `basic-pipeline-example.yml` to open.
## Inspect the output files
@@ -198,11 +198,11 @@ jobs:
```
</details>
Despite these 2 pipelines using different syntax they will function equivalently.
Despite these two pipelines using different syntax they will function equivalently.
## Perform a dry-run of a pipeline using `include`'d files
## Perform a dry-run migration of a pipeline using `include`'d files
The previous example demonstrated a basic pipeline that mapped exactly to concepts in GitHub Actions. In this section, we will perform a dry-run of the `included-files-example` pipeline that uses the `include` statement in GitLab:
The previous example demonstrated a basic pipeline that mapped exactly to concepts in GitHub Actions. In this section, you will perform a dry run of the `included-files-example` pipeline that uses the `include` statement in GitLab:
```yaml
include:
@@ -247,7 +247,7 @@ jobs:
It's important to note that Valet converted this into a single workflow without templates. This is because of fundamental differences in how GitLab templates and GitHub Actions templates (i.e. Reusable Workflows and Composite Actions) function in regards to job ordering. Unfortunately, elements of reusability will be sacrificed in order for the converted pipelines to function the same. It is likely that the output of Valet could be refactored to use [reusable workflow](https://docs.github.com/en/actions/using-workflows/reusing-workflows) at a later date.
As an added challenge, try constructing and running the `dry-run` command yourself. Hint, you should just have to change the project name.
As an added challenge, try constructing and running the `dry-run` command yourself. Hint, you should only have to change the project name.
## Next lab