About migrating from GitLab with GitHub Actions Importer
The instructions below will guide you through configuring your environment to use GitHub Actions Importer to migrate GitLab pipelines to GitHub Actions.
Prerequisites
- A GitLab account or organization with pipelines and jobs that you want to convert to GitHub Actions workflows.
- Access to create a GitLab personal access token for your account or organization.
- 一个可在其中运行基于 Linux 的容器并可安装所需工具的环境。
-
Docker 已安装并正在运行。
-
已安装 GitHub CLI。
注意
GitHub Actions Importer 容器和 CLI 不需要安装在 CI 平台所在的同一服务器上。
-
Limitations
There are some limitations on migrating processes automatically from GitLab pipelines to GitHub Actions with GitHub Actions Importer.
- Automatic caching in between jobs of different workflows is not supported.
- The
auditcommand is only supported when using an organization account. However, thedry-runandmigratecommands can be used with an organization or user account.
Manual tasks
Certain GitLab constructs must be migrated manually. These include:
- Masked project or group variable values
- Artifact reports
For more information on manual migrations, see Migrating from GitLab CI/CD to GitHub Actions.
Installing the GitHub Actions Importer CLI extension
-
安装 GitHub Actions Importer CLI 扩展：
Bash gh extension install github/gh-actions-importer
gh extension install github/gh-actions-importer -
验证是否已安装扩展：
$ gh actions-importer -h Options: -?, -h, --help Show help and usage information Commands: update Update to the latest version of GitHub Actions Importer. version Display the version of GitHub Actions Importer. configure Start an interactive prompt to configure credentials used to authenticate with your CI server(s). audit Plan your CI/CD migration by analyzing your current CI/CD footprint. forecast Forecast GitHub Actions usage from historical pipeline utilization. dry-run Convert a pipeline to a GitHub Actions workflow and output its yaml file. migrate Convert a pipeline to a GitHub Actions workflow and open a pull request with the changes.
Configuring credentials
The configure CLI command is used to set required credentials and options for GitHub Actions Importer when working with GitLab and GitHub.
-
Create a GitHub personal access token (classic). For more information, see 管理个人访问令牌.
Your token must have the
workflowscope.After creating the token, copy it and save it in a safe location for later use.
-
Create a GitLab personal access token. For more information, see Personal access tokens in the GitLab documentation.
Your token must have the
read_apiscope.After creating the token, copy it and save it in a safe location for later use.
-
In your terminal, run the GitHub Actions Importer
configureCLI command:gh actions-importer configureThe
configurecommand will prompt you for the following information:- For "Which CI providers are you configuring?", use the arrow keys to select
GitLab, press Space to select it, then press Enter. - For "Personal access token for GitHub", enter the value of the personal access token (classic) that you created earlier, and press Enter.
- For "Base url of the GitHub instance", press Enter to accept the default value (
https://github.com). - For "Private token for GitLab", enter the value for the GitLab personal access token that you created earlier, and press Enter.
- For "Base url of the GitLab instance", enter the URL of your GitLab instance, and press Enter.
An example of the output of the
configurecommand is shown below.$ gh actions-importer configure ✔ Which CI providers are you configuring?: GitLab Enter the following values (leave empty to omit): ✔ Personal access token for GitHub: *************** ✔ Base url of the GitHub instance: https://github.com ✔ Private token for GitLab: *************** ✔ Base url of the GitLab instance: http://localhost Environment variables successfully updated. - For "Which CI providers are you configuring?", use the arrow keys to select
-
In your terminal, run the GitHub Actions Importer
updateCLI command to connect to GitHub Packages Container registry and ensure that the container image is updated to the latest version:gh actions-importer updateThe output of the command should be similar to below:
Updating ghcr.io/actions-importer/cli:latest... ghcr.io/actions-importer/cli:latest up-to-date
Perform an audit of GitLab
You can use the audit command to get a high-level view of all pipelines in a GitLab server.
The audit command performs the following steps:
- Fetches all of the projects defined in a GitLab server.
- Converts each pipeline to its equivalent GitHub Actions workflow.
- Generates a report that summarizes how complete and complex of a migration is possible with GitHub Actions Importer.
Prerequisites for the audit command
In order to use the audit command, you must have a personal access token configured with a GitLab organization account.
Running the audit command
To perform an audit of a GitLab server, run the following command in your terminal, replacing my-gitlab-namespace with the namespace or group you are auditing:
gh actions-importer audit gitlab --output-dir tmp/audit --namespace my-gitlab-namespace
Inspecting the audit results
指定的输出目录中的文件包含审核结果。 有关审核结果的摘要，请参阅 audit_summary.md 文件。
审核摘要包含以下部分。
管道
“管道”部分包含有关由 GitHub Actions Importer 完成的转换率的概要统计信息。
下面列出了“管道”部分中可能出现的一些关键术语：
- “成功”管道已将所有管道构造和单个项目自动转换为其 GitHub Actions 等效项。
- “部分成功”管道已转换所有管道构造，但有一些单个项目未自动转换为其 GitHub Actions 等效项。
- “不受支持”管道是 GitHub Actions Importer 不支持的定义类型。
- “失败”管道在转换时遇到错误。 这可能是以下三个原因之一造成的：
- 该管道最初配置错误且无效。
- GitHub Actions Importer 在转换它时遇到内部错误。
- 网络响应失败，导致管道无法访问，这通常是由于凭据无效所致。
生成步骤
“生成步骤”部分概述了跨所有管道使用的各个生成步骤，以及由 GitHub Actions Importer 自动转换的生成步骤数。
下面列出了“生成步骤”部分中可能出现的一些关键术语：
- “已知”生成步骤是自动转换为等效操作的步骤。
- “未知”生成步骤是未自动转换为等效操作的步骤。
- “不受支持”生成步骤是满足以下任一条件的步骤：
- 从根本上不受 GitHub Actions 支持。
- 以与 GitHub Actions 不兼容的方式进行配置。
- “操作”是转换后的工作流中使用的操作的列表。 这对于以下情况可能很重要：
- 如果使用 GitHub Enterprise Server，收集要同步到实例的操作列表。
- 定义所使用的操作的组织级允许列表。 此操作列表是安全或合规性团队可能需要审查的操作的综合列表。
手动任务
“手动任务”部分概述了 GitHub Actions Importer 无法自动完成且必须由你手动完成的任务。
下面列出了“手动任务”部分中可能出现的一些关键术语：
- “机密”是在转换后的管道中使用的存储库或组织级机密。 必须在 GitHub Actions 中手动创建这些机密，才能使这些管道正常运行。 有关详细信息，请参阅“Using secrets in GitHub Actions”。
- “自托管运行器”是指在转换后的管道中引用的运行器（不是 GitHub 托管的运行器）的标签。 需要手动定义这些运行器，才能使这些管道正常运行。
文件
审核报告的最后一部分提供审核期间写入磁盘的所有文件的清单。
每个管道文件都包含审核中的各种文件，包括：
- GitHub 中定义的原始管道。
- 用于转换管道的任何网络响应。
- 转换后的工作流文件。
- 可用于排查管道转换失败问题的堆栈跟踪。
此外，workflow_usage.csv 文件包含一个以逗号分隔的列表，其中列出了每个成功转换的管道所使用的所有操作、机密和运行器。 这有助于确定哪些工作流使用哪些操作、机密或运行器，并且可用于进行安全评审。
Forecast potential build runner usage
You can use the forecast command to forecast potential GitHub Actions usage by computing metrics from completed pipeline runs in your GitLab server.
Running the forecast command
To perform a forecast of potential GitHub Actions usage, run the following command in your terminal, replacing my-gitlab-namespace with the namespace or group you are forecasting. By default, GitHub Actions Importer includes the previous seven days in the forecast report.
gh actions-importer forecast gitlab --output-dir tmp/forecast --namespace my-gitlab-namespace
Forecasting an entire namespace
To forecast an entire namespace and all of its subgroups, you must specify each subgroup in the --namespace argument or NAMESPACE environment variable.
For example:
gh actions-importer forecast gitlab --namespace my-gitlab-namespace my-gitlab-namespace/subgroup-one my-gitlab-namespace/subgroup-two ...
Inspecting the forecast report
The forecast_report.md file in the specified output directory contains the results of the forecast.
Listed below are some key terms that can appear in the forecast report:
- The job count is the total number of completed jobs.
- The pipeline count is the number of unique pipelines used.
- Execution time describes the amount of time a runner spent on a job. This metric can be used to help plan for the cost of GitHub-hosted runners.
- This metric is correlated to how much you should expect to spend in GitHub Actions. This will vary depending on the hardware used for these minutes. You can use the GitHub Actions pricing calculator to estimate the costs.
- Queue time metrics describe the amount of time a job spent waiting for a runner to be available to execute it.
- Concurrent jobs metrics describe the amount of jobs running at any given time. This metric can be used to define the number of runners you should configure.
Additionally, these metrics are defined for each queue of runners in GitLab. This is especially useful if there is a mix of hosted or self-hosted runners, or high or low spec machines, so you can see metrics specific to different types of runners.
Perform a dry-run migration of a GitLab pipeline
You can use the dry-run command to convert a GitLab pipeline to its equivalent GitHub Actions workflow.
Running the dry-run command
You can use the dry-run command to convert a GitLab pipeline to an equivalent GitHub Actions workflow. A dry-run creates the output files in a specified directory, but does not open a pull request to migrate the pipeline.
To perform a dry run of migrating your GitLab pipelines to GitHub Actions, run the following command in your terminal, replacing my-gitlab-project with your GitLab project slug, and my-gitlab-namespace with the namespace or group (full group path for subgroups, e.g. my-org/my-team) you are performing a dry run for.
gh actions-importer dry-run gitlab --output-dir tmp/dry-run --namespace my-gitlab-namespace --project my-gitlab-project
Inspecting the converted workflows
You can view the logs of the dry run and the converted workflow files in the specified output directory.
如果有任何 GitHub Actions Importer 无法自动转换的内容，例如未知生成步骤或部分成功管道，你可能需要创建自定义转换器来进一步自定义转换过程。 有关详细信息，请参阅“Extending GitHub Actions Importer with custom transformers”。
Perform a production migration of a GitLab pipeline
You can use the migrate command to convert a GitLab pipeline and open a pull request with the equivalent GitHub Actions workflow.
Running the migrate command
To migrate a GitLab pipeline to GitHub Actions, run the following command in your terminal, replacing the following values:
target-urlvalue with the URL for your GitHub repositorymy-gitlab-projectwith your GitLab project slugmy-gitlab-namespacewith the namespace or group you are migrating (full path for subgroups, e.g.my-org/my-team)
gh actions-importer migrate gitlab --target-url https://github.com/:owner/:repo --output-dir tmp/migrate --namespace my-gitlab-namespace --project my-gitlab-project
The command's output includes the URL to the pull request that adds the converted workflow to your repository. An example of a successful output is similar to the following:
$ gh actions-importer migrate gitlab --target-url https://github.com/octo-org/octo-repo --output-dir tmp/migrate --namespace octo-org --project monas-project
[2022-08-20 22:08:20] Logs: 'tmp/migrate/log/actions-importer-20220916-014033.log'
[2022-08-20 22:08:20] Pull request: 'https://github.com/octo-org/octo-repo/pull/1'
检查拉取请求
migrate 命令成功运行的输出包含一个指向新拉取请求的链接，此拉取请求将转换后的工作流添加到存储库。
拉取请求的一些重要元素包括：
- 在拉取请求说明中，有一个名为“手动步骤”的部分，其中列出了在完成将管道迁移到 GitHub Actions 之前必须手动完成的步骤。 例如，此部分可能会提供创建工作流中使用的任何机密。
- 转换后的工作流文件。 选择拉取请求中的“Files changed”选项卡，查看将添加到 GitHub 仓库的工作流文件****。
检查完拉取请求后，可以将其合并以将工作流添加到 GitHub 仓库。
Reference
This section contains reference information on environment variables, optional arguments, and supported syntax when using GitHub Actions Importer to migrate from GitLab.
Using environment variables
GitHub Actions Importer 使用环境变量进行身份验证配置。 这些变量在使用 configure 命令执行配置过程时设置。 有关详细信息，请参阅“配置凭据”部分。
GitHub Actions Importer uses the following environment variables to connect to your GitLab instance:
GITHUB_ACCESS_TOKEN: The personal access token (classic) used to create pull requests with a converted workflow (requires theworkflowscope).GITHUB_INSTANCE_URL: The URL to the target GitHub instance (for example,https://github.com).GITLAB_ACCESS_TOKEN: The GitLab personal access token used to view GitLab resources.GITLAB_INSTANCE_URL: The URL of the GitLab instance.NAMESPACE: The namespaces or groups that contain the GitLab pipelines.
These environment variables can be specified in a .env.local file that is loaded by GitHub Actions Importer when it is run.
Using optional arguments
有一些可选参数可以结合 GitHub Actions Importer 子命令使用来自定义迁移。
--source-file-path
You can use the --source-file-path argument with the forecast, dry-run, or migrate subcommands.
By default, GitHub Actions Importer fetches pipeline contents from source control. The --source-file-path argument tells GitHub Actions Importer to use the specified source file path instead.
For example:
gh actions-importer dry-run gitlab --output-dir output/ --namespace my-gitlab-namespace --project my-gitlab-project --source-file-path path/to/.gitlab-ci.yml
If you would like to supply multiple source files when running the forecast subcommand, you can use pattern matching in the file path value. The following example supplies GitHub Actions Importer with any source files that match the ./tmp/previous_forecast/jobs/*.json file path.
gh actions-importer forecast gitlab --output-dir output/ --namespace my-gitlab-namespace --project my-gitlab-project --source-file-path ./tmp/previous_forecast/jobs/*.json
--config-file-path
You can use the --config-file-path argument with the audit, dry-run, and migrate subcommands.
By default, GitHub Actions Importer fetches pipeline contents from source control. The --config-file-path argument tells GitHub Actions Importer to use the specified source files instead.
The --config-file-path argument can also be used to specify which repository a converted reusable workflow should be migrated to.
Audit example
In this example, GitHub Actions Importer uses the specified YAML configuration file to perform an audit.
gh actions-importer audit gitlab --output-dir path/to/output/ --namespace my-gitlab-namespace --config-file-path path/to/gitlab/config.yml
To audit a GitLab instance using a configuration file, the file must be in the following format, and each repository_slug value must be unique:
source_files:
- repository_slug: namespace/project-name
path: path/to/.gitlab-ci.yml
- repository_slug: namespace/some-other-project-name
path: path/to/.gitlab-ci.yml
Dry run example
In this example, GitHub Actions Importer uses the specified YAML configuration file as the source file to perform a dry run.
The pipeline is selected by matching the repository_slug in the configuration file to the value of the --namespace and --project options. The path is then used to pull the specified source file.
gh actions-importer dry-run gitlab --namespace my-gitlab-namespace --project my-gitlab-project-name --output-dir ./output/ --config-file-path ./path/to/gitlab/config.yml
Specify the repository of converted reusable workflows
GitHub Actions Importer uses the YAML file provided to the --config-file-path argument to determine the repository that converted reusable workflows are migrated to.
To begin, you should run an audit without the --config-file-path argument:
gh actions-importer audit gitlab --output-dir ./output/
The output of this command will contain a file named config.yml that contains a list of all the composite actions that were converted by GitHub Actions Importer. For example, the config.yml file may have the following contents:
reusable_workflows:
- name: my-reusable-workflow.yml
target_url: https://github.com/octo-org/octo-repo
ref: main
You can use this file to specify which repository and ref a reusable workflow or composite action should be added to. You can then use the --config-file-path argument to provide the config.yml file to GitHub Actions Importer. For example, you can use this file when running a migrate command to open a pull request for each unique repository defined in the config file:
gh actions-importer migrate gitlab --project my-project-name --output-dir output/ --config-file-path config.yml --target-url https://github.com/my-org/my-repo
Supported syntax for GitLab pipelines
The following table shows the type of properties GitHub Actions Importer is currently able to convert. For more details about how GitLab pipeline syntax aligns with GitHub Actions, see Migrating from GitLab CI/CD to GitHub Actions.
| GitLab Pipelines | GitHub Actions | Status |
|---|---|---|
after_script | jobs.<job_id>.steps | Supported |
auto_cancel_pending_pipelines | concurrency | Supported |
before_script | jobs.<job_id>.steps | Supported |
build_timeout or timeout | jobs.<job_id>.timeout-minutes | Supported |
default | Not applicable | Supported |
image | jobs.<job_id>.container | Supported |
job | jobs.<job_id> | Supported |
needs | jobs.<job_id>.needs | Supported |
only_allow_merge_if_pipeline_succeeds | on.pull_request | Supported |
resource_group | jobs.<job_id>.concurrency | Supported |
schedule | on.schedule | Supported |
script | jobs.<job_id>.steps | Supported |
stages | jobs | Supported |
tags | jobs.<job_id>.runs-on | Supported |
variables | env, jobs.<job_id>.env | Supported |
| Run pipelines for new commits | on.push | Supported |
| Run pipelines manually | on.workflow_dispatch | Supported |
environment | jobs.<job_id>.environment | Partially supported |
include | Files referenced in an include statement are merged into a single job graph before being transformed. | Partially supported |
only or except | jobs.<job_id>.if | Partially supported |
parallel | jobs.<job_id>.strategy | Partially supported |
rules | jobs.<job_id>.if | Partially supported |
services | jobs.<job_id>.services | Partially supported |
workflow | if | Partially supported |
For information about supported GitLab constructs, see the github/gh-actions-importer repository.
Environment variables syntax
GitHub Actions Importer uses the mapping in the table below to convert default GitLab environment variables to the closest equivalent in GitHub Actions.
| GitLab | GitHub Actions |
|---|---|
CI_API_V4_URL | ${{ github.api_url }} |
CI_BUILDS_DIR | ${{ github.workspace }} |
CI_COMMIT_BRANCH | ${{ github.ref }} |
CI_COMMIT_REF_NAME | ${{ github.ref }} |
CI_COMMIT_REF_SLUG | ${{ github.ref }} |
CI_COMMIT_SHA | ${{ github.sha }} |
CI_COMMIT_SHORT_SHA | ${{ github.sha }} |
CI_COMMIT_TAG | ${{ github.ref }} |
CI_JOB_ID | ${{ github.job }} |
CI_JOB_MANUAL | ${{ github.event_name == 'workflow_dispatch' }} |
CI_JOB_NAME | ${{ github.job }} |
CI_JOB_STATUS | ${{ job.status }} |
CI_JOB_URL | ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }} |
CI_JOB_TOKEN | ${{ github.token }} |
CI_NODE_INDEX | ${{ strategy.job-index }} |
CI_NODE_TOTAL | ${{ strategy.job-total }} |
CI_PIPELINE_ID | ${{ github.repository}}/${{ github.workflow }} |
CI_PIPELINE_IID | ${{ github.workflow }} |
CI_PIPELINE_SOURCE | ${{ github.event_name }} |
CI_PIPELINE_TRIGGERED | ${{ github.actions }} |
CI_PIPELINE_URL | ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }} |
CI_PROJECT_DIR | ${{ github.workspace }} |
CI_PROJECT_ID | ${{ github.repository }} |
CI_PROJECT_NAME | ${{ github.event.repository.name }} |
CI_PROJECT_NAMESPACE | ${{ github.repository_owner }} |
CI_PROJECT_PATH_SLUG | ${{ github.repository }} |
CI_PROJECT_PATH | ${{ github.repository }} |
CI_PROJECT_ROOT_NAMESPACE | ${{ github.repository_owner }} |
CI_PROJECT_TITLE | ${{ github.event.repository.full_name }} |
CI_PROJECT_URL | ${{ github.server_url }}/${{ github.repository }} |
CI_REPOSITORY_URL | ${{ github.event.repository.clone_url }} |
CI_RUNNER_EXECUTABLE_ARCH | ${{ runner.os }} |
CI_SERVER_HOST | ${{ github.server_url }} |
CI_SERVER_URL | ${{ github.server_url }} |
CI_SERVER | ${{ github.actions }} |
GITLAB_CI | ${{ github.actions }} |
GITLAB_USER_EMAIL | ${{ github.actor }} |
GITLAB_USER_ID | ${{ github.actor }} |
GITLAB_USER_LOGIN | ${{ github.actor }} |
GITLAB_USER_NAME | ${{ github.actor }} |
TRIGGER_PAYLOAD | ${{ github.event_path }} |
CI_MERGE_REQUEST_ASSIGNEES | ${{ github.event.pull_request.assignees }} |
CI_MERGE_REQUEST_ID | ${{ github.event.pull_request.number }} |
CI_MERGE_REQUEST_IID | ${{ github.event.pull_request.number }} |
CI_MERGE_REQUEST_LABELS | ${{ github.event.pull_request.labels }} |
CI_MERGE_REQUEST_MILESTONE | ${{ github.event.pull_request.milestone }} |
CI_MERGE_REQUEST_PROJECT_ID | ${{ github.repository }} |
CI_MERGE_REQUEST_PROJECT_PATH | ${{ github.repository }} |
CI_MERGE_REQUEST_PROJECT_URL | ${{ github.server_url }}/${{ github.repository }} |
CI_MERGE_REQUEST_REF_PATH | ${{ github.ref }} |
CI_MERGE_REQUEST_SOURCE_BRANCH_NAME | ${{ github.event.pull_request.head.ref }} |
CI_MERGE_REQUEST_SOURCE_BRANCH_SHA | ${{ github.event.pull_request.head.sha}} |
CI_MERGE_REQUEST_SOURCE_PROJECT_ID | ${{ github.event.pull_request.head.repo.full_name }} |
CI_MERGE_REQUEST_SOURCE_PROJECT_PATH | ${{ github.event.pull_request.head.repo.full_name }} |
CI_MERGE_REQUEST_SOURCE_PROJECT_URL | ${{ github.event.pull_request.head.repo.url }} |
CI_MERGE_REQUEST_TARGET_BRANCH_NAME | ${{ github.event.pull_request.base.ref }} |
CI_MERGE_REQUEST_TARGET_BRANCH_SHA | ${{ github.event.pull_request.base.sha }} |
CI_MERGE_REQUEST_TITLE | ${{ github.event.pull_request.title }} |
CI_EXTERNAL_PULL_REQUEST_IID | ${{ github.event.pull_request.number }} |
CI_EXTERNAL_PULL_REQUEST_SOURCE_REPOSITORY | ${{ github.event.pull_request.head.repo.full_name }} |
CI_EXTERNAL_PULL_REQUEST_TARGET_REPOSITORY | ${{ github.event.pull_request.base.repo.full_name }} |
CI_EXTERNAL_PULL_REQUEST_SOURCE_BRANCH_NAME | ${{ github.event.pull_request.head.ref }} |
CI_EXTERNAL_PULL_REQUEST_SOURCE_BRANCH_SHA | ${{ github.event.pull_request.head.sha }} |
CI_EXTERNAL_PULL_REQUEST_TARGET_BRANCH_NAME | ${{ github.event.pull_request.base.ref }} |
CI_EXTERNAL_PULL_REQUEST_TARGET_BRANCH_SHA | ${{ github.event.pull_request.base.sha }} |
Legal notice
部分内容改编自 MIT 许可证下的 https://github.com/github/gh-actions-importer/ ：
MIT License
Copyright (c) 2022 GitHub
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.