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

Updating AzDO labs

Browse Source
This commit is contained in:
Ethan Dennis
2022-11-03 12:42:11 -07:00
parent 5748bfb279
commit 5a4aa125ae
3 changed files with 16 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
azure_devops/1-configure.md
+5 -5
View File
@@ -1,6 +1,6 @@
# Configure credentials for Valet # Configure credentials for GitHub Actions Importer
In this lab, you will use the `configure` CLI command to set the required credentials and information for Valet to use when working with Azure DevOps and GitHub. In this lab, you will use the `configure` CLI command to set the required credentials and information for GitHub Actions Importer to use when working with Azure DevOps and GitHub.
You will need to complete all of the setup instructions [here](./readme.md#configure-your-codespace) prior to performing this lab. You will need to complete all of the setup instructions [here](./readme.md#configure-your-codespace) prior to performing this lab.
@@ -66,7 +66,7 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
## Verify your environment ## Verify your environment
To verify our environment is configured correctly, run the `update` CLI command. The `update` CLI command will download the latest version of Valet to your codespace. To verify our environment is configured correctly, run the `update` CLI command. The `update` CLI command will download the latest version of GitHub Actions Importer to your codespace.
1. In the codespace terminal, run the following command: 1. In the codespace terminal, run the following command:
@@ -74,12 +74,12 @@ To verify our environment is configured correctly, run the `update` CLI command.
gh actions-importer update gh actions-importer update
``` ```
2. You should see a confirmation that you were logged into the GitHub Container Registry and Valet was updated to the latest version. 2. You should see a confirmation that you were logged into the GitHub Container Registry and the image was updated to the latest version.
```console ```console
$ gh actions-importer update $ gh actions-importer update
Login Succeeded Login Succeeded
latest: Pulling from valet-customers/valet-cli latest: Pulling from actions-importer/cli
Digest: sha256:a7d00dee8a37e25da59daeed44b1543f476b00fa2c41c47f48deeaf34a215bbb Digest: sha256:a7d00dee8a37e25da59daeed44b1543f476b00fa2c41c47f48deeaf34a215bbb
Status: Image is up to date for ghcr.io/actions-importer/cli:latest Status: Image is up to date for ghcr.io/actions-importer/cli:latest
ghcr.io/actions-importer/cli:latest ghcr.io/actions-importer/cli:latest
azure_devops/2-audit.md
+10 -8
View File
@@ -3,9 +3,10 @@
In this lab, you will use the `audit` command to get a high-level view of all pipelines in an Azure DevOps organization or project. In this lab, you will use the `audit` command to get a high-level view of all pipelines in an Azure DevOps organization or project.
The `audit` command will perform the following steps: The `audit` command will perform the following steps:
1. Fetch all of the projects defined in an Azure DevOps organization. 1. Fetch all of the projects defined in an Azure DevOps organization.
2. Convert each pipeline to their equivalent GitHub Actions workflow. 2. Convert each pipeline to their equivalent GitHub Actions workflow.
3. Generate a report that summarizes how complete and complex of a migration is possible with Valet. 3. Generate a report that summarizes how complete and complex of a migration is possible with GitHub Actions Importer.
## Prerequisites ## Prerequisites
@@ -23,7 +24,7 @@ You will now perform an audit against the bootstrapped Azure DevOps project. Ans
- __:project__. This should be the same project name used in the setup steps [here](./readme.md#bootstrap-your-azure-devops-organization) - __:project__. This should be the same project name used in the setup steps [here](./readme.md#bootstrap-your-azure-devops-organization)
3. Where do you want to store the result? 3. Where do you want to store the result?
- __tmp/audit__. This can be any path within the working directory from which Valet commands are executed. - __tmp/audit__. This can be any path within the working directory from which GitHub Actions Importer commands are executed.
### Steps ### Steps
@@ -48,7 +49,7 @@ You will now perform an audit against the bootstrapped Azure DevOps project. Ans
#### Pipelines #### Pipelines
The pipeline summary section contains high level statistics regarding the conversion rate done by Valet: The pipeline summary section contains high level statistics regarding the conversion rate done by GitHub Actions Importer:
```md ```md
## Pipelines ## Pipelines
@@ -72,20 +73,20 @@ Here are some key terms in the "Pipelines" section in the above example:
- __Successful__ pipelines had 100% of the pipeline constructs and individual items converted automatically to their GitHub Actions equivalent. - __Successful__ pipelines had 100% of the pipeline constructs and individual items converted automatically to their GitHub Actions equivalent.
- __Partially successful__ pipelines had all of the pipeline constructs converted, however, there were some individual items (e.g. build tasks or build triggers) that were not converted automatically to their GitHub Actions equivalent. - __Partially successful__ pipelines had all of the pipeline constructs converted, however, there were some individual items (e.g. build tasks or build triggers) that were not converted automatically to their GitHub Actions equivalent.
- __Unsupported__ pipelines are definition types that are not supported by Valet. The following Azure DevOps pipeline types are supported: - __Unsupported__ pipelines are definition types that are not supported by GitHub Actions Importer. The following Azure DevOps pipeline types are supported:
- Classic (designer) - Classic (designer)
- YAML - YAML
- Release - Release
- __Failed__ pipelines encountered a fatal error when being converted. This can occur for one of three reasons: - __Failed__ pipelines encountered a fatal error when being converted. This can occur for one of three reasons:
- The pipeline was misconfigured and not valid in Azure DevOps. - The pipeline was misconfigured and not valid in Azure DevOps.
- Valet encountered an internal error when converting it. - GitHub Actions Importer encountered an internal error when converting it.
- There was an unsuccessful network response, often due to invalid credentials, that caused the pipeline to be inaccessible. - There was an unsuccessful network response, often due to invalid credentials, that caused the pipeline to be inaccessible.
The "Job types" section will summarize which types of pipelines are being used and which are supported or unsupported by Valet. The "Job types" section will summarize which types of pipelines are being used and which are supported or unsupported by GitHub Actions Importer.
#### Build steps #### Build steps
The build steps summary section presents an overview of the individual build steps that are used across all pipelines and how many were automatically converted by Valet. The build steps summary section presents an overview of the individual build steps that are used across all pipelines and how many were automatically converted by GitHub Actions Importer.
```md ```md
### Build steps ### Build steps
@@ -125,7 +126,7 @@ There is an equivalent breakdown of build triggers, environment variables, and o
#### Manual Tasks #### Manual Tasks
The manual tasks summary section presents an overview of the manual tasks that you will need to perform that Valet is not able to complete automatically. The manual tasks summary section presents an overview of the manual tasks that you will need to perform that GitHub Actions Importer is not able to complete automatically.
```md ```md
### Manual tasks ### Manual tasks
@@ -196,6 +197,7 @@ Each pipeline will have a variety of files written that include:
``` ```
The contents of this file can be useful in answering questions similar to the following: The contents of this file can be useful in answering questions similar to the following:
- What workflows will depend on which actions? - What workflows will depend on which actions?
- What workflows use an action that must go through a security review? - What workflows use an action that must go through a security review?
- What workflows use specific secrets? - What workflows use specific secrets?
readme.md
+1 -1
View File
@@ -1,6 +1,6 @@
# GitHub Actions Importer learning labs # GitHub Actions Importer learning labs
GitHub Actions Importer helps you plan and automate the migration of Azure DevOps, CircleCI, GitLab, Jenkins, and Travis CI pipelines to GitHub Actions. This repository contains learning paths that teach you how to use GitHub Actions Importer and how to approach migrations to Actions. [GitHub Actions Importer](https://docs.github.com/en/actions/migrating-to-github-actions/automating-migration-with-github-actions-importer) helps plan, forecast, and automate the migration of Azure DevOps, CircleCI, GitLab, Jenkins, and Travis CI pipelines to GitHub Actions. This repository contains learning paths that teach you how to use GitHub Actions Importer and how to approach migrations to Actions.
> **Note**: GitHub Actions Importer is currently available as a public preview. Visit the [sign up page](https://github.com/features/actions-importer/signup) to request access to the preview. > **Note**: GitHub Actions Importer is currently available as a public preview. Visit the [sign up page](https://github.com/features/actions-importer/signup) to request access to the preview.