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

Merge pull request #62 from valet-customers/luke-audit-changes

Browse Source 
Change audit summary to a list
This commit is contained in:
Luke Cheung Engle
2022-09-16 12:52:39 -07:00
committed by GitHub
parent bbe9385689 a9f9e4cd20
commit 097dd945d2
4 changed files with 16 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
azure_devops/2-audit.md
+4 -1
View File
@@ -2,7 +2,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 operates by fetching all of the pipelines defined in an Azure DevOps organization or project, converting each to their equivalent GitHub Actions workflow, and writing a report that summarizes how complete and complex of a migration is possible with Valet. The `audit` command will perform the following steps:
1. Fetch all of the projects defined in an Azure DevOps organization.
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.
## Prerequisites ## Prerequisites
circle_ci/2-audit.md
+4 -1
View File
@@ -2,7 +2,10 @@
In this lab, you will use the `audit` command to get a high-level view of all projects in a CircleCI organization. In this lab, you will use the `audit` command to get a high-level view of all projects in a CircleCI organization.
The `audit` command operates by fetching all of the projects defined in a CircleCI organization, converting each to their equivalent GitHub Actions workflow, and writing a report that summarizes how complete and complex of a migration is possible with Valet. The `audit` command will perform the following steps:
1. Fetch all of the projects defined in an CircleCI organization.
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.
## Prerequisites ## Prerequisites
gitlab/2-audit.md
+4 -1
View File
@@ -2,7 +2,10 @@
In this lab, you will use the `audit` command to get a high-level view of all pipelines in a GitLab server. In this lab, you will use the `audit` command to get a high-level view of all pipelines in a GitLab server.
The `audit` command operates by fetching all of the pipelines defined in a GitLab server, converting each to their equivalent GitHub Actions workflow, and writing a report that summarizes how complete and complex of a migration is possible with Valet. The `audit` command will perform the following steps:
1. Fetch all of the projects defined in a GitLab group.
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.
## Prerequisites ## Prerequisites
jenkins/2-audit.md
+4 -1
View File
@@ -2,7 +2,10 @@
In this lab, you will use the `audit` command to get a high-level view of all pipelines in a Jenkins server. In this lab, you will use the `audit` command to get a high-level view of all pipelines in a Jenkins server.
The `audit` command operates by fetching all of the pipelines defined in a Jenkins server, converting each to their equivalent GitHub Actions workflow, and writing a report that summarizes how complete and complex of a migration is possible with Valet. The `audit` command will perform the following steps:
1. Fetch all of the projects defined in a Jenkins server.
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.
## Prerequisites ## Prerequisites