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

Add some more revisions of cci labs

Browse Source
This commit is contained in:
Ethan Dennis
2022-09-16 09:37:46 -07:00
parent f5bb8a4691
commit bbe9385689
16 changed files with 38 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files
azure_devops/5-custom-transformers.md
+2 -2
View File
@@ -12,7 +12,7 @@ In this lab we will build upon the `dry-run` command to override Valet's default
1. Followed the steps [here](./readme.md#configure-your-codespace) to set up your GitHub Codespaces environment and bootstrap an Azure DevOps project.
2. Completed the [configure lab](./1-configure-lab.md#configuring-credentials).
3. Completed the [audit lab](./2-audit.md).
4. Completed the [dry-run lab](./3-dry-run.md).
4. Completed the [dry-run lab](./4-dry-run.md).
## Perform a dry run
@@ -77,7 +77,7 @@ jobs:
</details>
_Note_: You can refer to the previous [lab](./3-dry-run.md) to learn about the fundamentals of the `dry-run` command.
_Note_: You can refer to the previous [lab](./4-dry-run.md) to learn about the fundamentals of the `dry-run` command.
## Custom transformers for build steps
azure_devops/6-migrate.md
+2 -2
View File
@@ -6,8 +6,8 @@ In this lab, you will use the `migrate` command to convert an Azure DevOps pipel
1. Followed the steps [here](./readme.md#configure-your-codespace) to set up your GitHub Codespaces environment and bootstrap an Azure DevOps project.
2. Completed the [configure lab](./1-configure-lab.md#configuring-credentials).
3. Completed the [dry-run lab](./3-dry-run.md).
4. Completed the [custom transformers lab](./4-custom-transformers.md).
3. Completed the [dry-run lab](./4-dry-run.md).
4. Completed the [custom transformers lab](./5-custom-transformers.md).
## Performing a migration
azure_devops/readme.md
+4 -4
View File
@@ -77,10 +77,10 @@ Perform the following labs to learn how to migrate Azure DevOps pipelines to Git
1. [Configure credentials for Valet](1-configure.md)
2. [Perform an audit of an Azure DevOps project](2-audit.md)
3. [Perform a dry-run migration of an Azure DevOps pipeline](3-dry-run.md)
4. [Use custom transformers to customize Valet's behavior](4-custom-transformers.md)
5. [Perform a production migration of a Azure DevOps pipeline](5-migrate.md)
6. [Forecast potential build runner usage](6-forecast.md)
3. [Forecast potential build runner usage](3-forecast.md)
4. [Perform a dry-run migration of an Azure DevOps pipeline](4-dry-run.md)
5. [Use custom transformers to customize Valet's behavior](5-custom-transformers.md)
6. [Perform a production migration of a Azure DevOps pipeline](6-migrate.md)
## Troubleshoot the Valet CLI
circle_ci/1-configure.md
-1
View File
@@ -34,7 +34,6 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
![configure-screenshot](https://user-images.githubusercontent.com/18723510/188935436-308fa6d3-6eb7-48b9-bbf0-20ab0cdae411.png)
## Verify your environment
To verify our environment is configured correctly, we are going to run the `update` CLI command. The `update` CLI command will download the latest version of Valet to your codespace.
circle_ci/2-audit.md
+1 -1
View File
@@ -11,7 +11,7 @@ The `audit` command operates by fetching all of the projects defined in a Circle
## Perform an audit
We will be performing an audit against the **labs-data** organization in CircleCI, which was created for the purposes of this lab. Valet was already been set to use this organization during the configure lab. The only remaining information needed for the `audit` command is:
You will be performing an `audit` for the __labs-data__ CircleCI organization that was created for the purposes of these labs. Your environment was configured to use this organization during the [configure lab](./1-configure.md). The remaining information needed to perform an `audit` is:
1. Where do we want to store the result?
- __./tmp/audit__. This can be any path within the working directory that Valet commands are executed from.
circle_ci/3-forecast.md
+1
View File
@@ -10,6 +10,7 @@ In this lab you will use the `forecast` command to forecast potential GitHub Act
## Perform a forecast
Answer the following questions before running the `forecast` command:
1. What is the date you want to start forecasting from?
- **2022-09-02**. This date is needed as it is prior to when the bulk of builds were trigger in the demo CircleCI organization for these labs. This value defaults to the date one week ago, however, you should use a start date that will show a representative view of typical usage.
2. Where do you want to store the results?
circle_ci/4-dry-run.md
+3 -5
View File
@@ -1,4 +1,4 @@
# Perform a dry-run of a CircleCI pipeline
# Perform a dry-run migration of a CircleCI pipeline
In this lab you will use the `dry-run` command to convert a CircleCI pipeline to its equivalent GitHub Actions workflow.
@@ -10,7 +10,7 @@ In this lab you will use the `dry-run` command to convert a CircleCI pipeline to
## Perform a dry run
You will be performing a dry-run against a CircleCI project. Answer the following questions before running this command:
You will be performing a dry run migration against a CircleCI project. Answer the following questions before running this command:
1. What project do you want to convert?
- __circleci-demo-ruby-rails__. This is one of the sample projects avaiable in the CircleCI labs-data organization.
@@ -31,12 +31,10 @@ You will be performing a dry-run against a CircleCI project. Answer the followin
![command-result](https://user-images.githubusercontent.com/18723510/189911131-bf6bfd6f-2b5e-4e49-8d14-95ef9c312117.png)
4. View the converted workflow:
- Find `./tmp/dry-run-lab/labs-data/circleci-demo-ruby-rails` in the file explorer pane in your codespace.
- Click `build_and_test.yml` to open.
## Inspect the output files
The files generated from the `dry-run` command represent the equivalent Actions workflow for the CircleCI project. The CircleCI configuration and converted workflow can be seen below:
circle_ci/5-custom-transformers.md
+3 -3
View File
@@ -11,7 +11,7 @@ In this lab you will build upon the `dry-run` command to override Valet's defaul
1. Followed the steps [here](./readme.md#configure-your-codespace) to set up your GitHub Codespaces environment.
2. Completed the [configure lab](./1-configure.md#configuring-credentials).
3. Completed the [dry-run lab](./3-dry-run.md).
3. Completed the [dry-run lab](./4-dry-run.md).
## Perform a dry-run
@@ -60,7 +60,7 @@ jobs:
</details>
_Note_: You can refer to the previous [lab](./3-dry-run.md) to learn about the fundamentals of the `dry-run` command.
_Note_: You can refer to the previous [lab](./4-dry-run.md) to learn about the fundamentals of the `dry-run` command.
## Custom transformers for an unknown step
@@ -145,7 +145,7 @@ Now you can perform another `dry-run` command with the `--custom-transformers` C
+. COVERAGE_DIR: "$RUNNER_TEMP/cov"
```
## Custom transformers for resource class:
## Custom transformers for resource class
You can also use custom transformers to change the runner for a job that defines a `resource_class` attribute. In the example pipeline, the `setup` job uses a `resource_class` of `large` to dictate the machine used to execute the job. In this scenario, you may want to use this value to perform the `setup` job on a runner with the label of `some-large-runner` in Actions.
circle_ci/6-migrate.md
+2 -2
View File
@@ -6,8 +6,8 @@ In this lab, you will use the `migrate` command to convert a CircleCI pipeline a
1. Followed the steps [here](./readme.md#configure-your-codespace) to set up your GitHub Codespaces environment.
2. Completed the [configure lab](./1-configure.md#configuring-credentials).
3. Completed the [dry-run lab](./3-dry-run.md).
4. Completed the [custom transformers lab](./4-custom-transformers.md).
3. Completed the [dry-run lab](./4-dry-run.md).
4. Completed the [custom transformers lab](./5-custom-transformers.md).
## Performing a migration
circle_ci/readme.md
+4 -4
View File
@@ -41,10 +41,10 @@ Perform the following labs to test-drive Valet
1. [Configure credentials for Valet](1-configure.md)
2. [Perform an audit of CircleCI](2-audit.md)
3. [Perform a dry-run of a CircleCI pipeline](3-dry-run.md)
4. [Use custom transformers to customize Valet's behavior](4-custom-transformers.md)
5. [Perform a production migration of a CircleCI pipeline](5-migrate.md)
6. [Forecast potential build runner usage](6-forecast.md)
3. [Forecast potential build runner usage](3-forecast.md)
4. [Perform a dry-run of a CircleCI pipeline](4-dry-run.md)
5. [Use custom transformers to customize Valet's behavior](5-custom-transformers.md)
6. [Perform a production migration of a CircleCI pipeline](6-migrate.md)
## Troubleshoot the Valet CLI
gitlab/5-custom-transformers.md
+2 -2
View File
@@ -11,7 +11,7 @@ In this lab you will build upon the `dry-run` command to override Valet's defaul
1. Followed the steps [here](./readme.md#configure-your-codespace) to set up your GitHub Codespaces environment and start you GitLab server.
2. Completed the [configure lab](./1-configure-lab.md#configuring-credentials).
3. Completed the [dry-run lab](./3-dry-run.md).
3. Completed the [dry-run lab](./4-dry-run.md).
## Perform a dry-run
@@ -53,7 +53,7 @@ jobs:
</details>
_Note_: You can refer to the previous [lab](./3-dry-run.md) to learn about the fundamentals of the `dry-run` command.
_Note_: You can refer to the previous [lab](./4-dry-run.md) to learn about the fundamentals of the `dry-run` command.
## Custom transformers for an unknown step
gitlab/6-migrate.md
+2 -2
View File
@@ -6,8 +6,8 @@ In this lab, you will use the `migrate` command to convert a GitLab pipeline and
1. Followed the steps [here](./readme.md#configure-your-codespace) to set up your GitHub Codespaces environment and start a GitLab server.
2. Completed the [configure lab](./1-configure-lab.md#configuring-credentials).
3. Completed the [dry-run lab](./3-dry-run.md).
4. Completed the [custom transformers lab](./4-custom-transformers.md).
3. Completed the [dry-run lab](./4-dry-run.md).
4. Completed the [custom transformers lab](./5-custom-transformers.md).
## Performing a migration
gitlab/readme.md
+4 -4
View File
@@ -61,10 +61,10 @@ Perform the following labs to learn more about Actions migrations with Valet:
1. [Configure credentials for Valet](1-configure.md)
2. [Perform an audit on GitLab pipelines](2-audit.md)
3. [Perform a dry-run migration of a GitLab pipeline](3-dry-run.md)
4. [Use custom transformers to customize Valet's behavior](4-custom-transformers.md)
5. [Perform a production migration of a GitLab pipeline](5-migrate.md)
6. [Forecast potential build runner usage](6-forecast.md)
3. [Forecast potential build runner usage](3-forecast.md)
4. [Perform a dry-run migration of a GitLab pipeline](4-dry-run.md)
5. [Use custom transformers to customize Valet's behavior](5-custom-transformers.md)
6. [Perform a production migration of a GitLab pipeline](6-migrate.md)
## Troubleshoot the Valet CLI
jenkins/5-custom-transformers.md
+2 -2
View File
@@ -11,7 +11,7 @@ In this lab you will build upon the `dry-run` command to override Valet's defaul
1. Followed the steps [here](./readme.md#configure-your-codespace) to set up your GitHub Codespaces environment and start a Jenkins server.
2. Completed the [configure lab](./1-configure-lab.md#configuring-credentials).
3. Completed the [dry-run lab](./3-dry-run.md).
3. Completed the [dry-run lab](./4-dry-run.md).
## Perform a dry-run
@@ -71,7 +71,7 @@ jobs:
</details>
_Note_: You can refer to the previous [lab](./3-dry-run.md) to learn about the fundamentals of the `dry-run` command.
_Note_: You can refer to the previous [lab](./4-dry-run.md) to learn about the fundamentals of the `dry-run` command.
## Custom transformers for an unknown step
jenkins/6-migrate.md
+2 -2
View File
@@ -6,8 +6,8 @@ In this lab, you will use the `migrate` command to convert a Jenkins pipeline an
1. Followed the steps [here](./readme.md#configure-your-codespace) to set up your GitHub Codespaces environment and start a Jenkins server.
2. Completed the [configure lab](./1-configure-lab.md#configuring-credentials).
3. Completed the [dry-run lab](./3-dry-run.md).
4. Completed the [custom transformers lab](./4-custom-transformers.md).
3. Completed the [dry-run lab](./4-dry-run.md).
4. Completed the [custom transformers lab](./5-custom-transformers.md).
## Performing a migration
jenkins/readme.md
+4 -4
View File
@@ -61,10 +61,10 @@ Perform the following labs to learn more about Actions migrations with Valet:
1. [Configure credentials for Valet](1-configure.md)
2. [Perform an audit of a Jenkins server](2-audit.md)
3. [Perform a dry-run migration of a Jenkins pipeline](3-dry-run.md)
4. [Use custom transformers to customize Valet's behavior](4-custom-transformers.md)
5. [Perform a production migration of a Jenkins pipeline](5-migrate.md)
6. [Forecast potential build runner usage](6-forecast.md)
3. [Forecast potential build runner usage](3-forecast.md)
4. [Perform a dry-run migration of a Jenkins pipeline](4-dry-run.md)
5. [Use custom transformers to customize Valet's behavior](5-custom-transformers.md)
6. [Perform a production migration of a Jenkins pipeline](6-migrate.md)
## Troubleshoot the Valet CLI