Alibaba Cloud DevOps:Install Migration Tool

Migration Objects

• Self-managed GitLab repositories: Supports migration of Git code data, user permissions, webhooks, protected branches, and open merge requests.

• Git code data from common third-party platform repositories, such as Gitee, Coding, and GitHub.

• Existing local repositories.

Procedure

• Step 1: Download the tool

• Step 2: Install the tool

• Step 3: Test and validate

• Step 4: Select a scenario

• Step 5: Related steps (optional)

Step 1: Download the tool

Download the migration tool based on your operating system and the site you want to migrate:

Step 2: Install the tool

The Codeup-CLI tool is ready to use after download. Place the downloaded and unzipped tool in the directory where you run command-line tools, as follows:

# Create a new local workspace. You can customize the name, such as "workspace". Delete it after migration:
mkdir workspace
cd workspace

# Place the downloaded codeup-cli tool in your actual workspace directory
cp ~/Downloads/codeup-cli ./

# Create a new directory to store third-party repositories to be migrated. You can customize the name, such as "repo"
mkdir repo

Step 3: Test and validate

For example, on Linux, execute the following command in the command line to confirm that the tool runs normally:

./codeup-cli --help

Handle error messages:

• If an error message indicates insufficient permissions to run the tool, on Linux or macOS, execute the following command to grant authorization:

  chmod +x ./codeup-cli

• If the following message appears, it indicates that the downloaded tool package does not match your system type. Confirm your system type and download the corresponding tool package again.

  Bad CPU type in executable

Step 4: Select a scenario

If the tool runs normally as validated above, select a suitable migration scenario based on your requirements and platform type:

• Self-managed GitLab migration.

• General third-party code platform migration (such as GitHub, Gitee, and Coding).

• Batch migration of existing local repositories.

Step 5: Related steps (optional)

1. Apsara DevOps code push/pull authentication settings: When developers use the new Apsara DevOps platform to push or pull code, configure authentication information:

• If using SSH, for configuration instructions, see Configure SSH Key.

2. Update repository address: After import, update the repository address to the new repository address on Apsara DevOps.

• Update local repository remote address:

  # View the currently configured remote: Execute 
  git remote -v
  # Replace the currently configured remote (default origin): Execute 
  git remote set-url origin <new git clone address on Apsara Devops>

• Update third-party system push/pull repository address:

  • If a third-party system pushes or pulls code, manually replace the repository address configured on the third-party system.

  • If the third-party system uses HTTPS to push or pull code, also update the push/pull account and password parameters configured on the third-party system to ensure it can access the Apsara DevOps repository normally.