Container Registry supports building images from source code repositories, including Alibaba Cloud Codeup, GitHub, GitLab, Git, and Gitee. Images can be rebuilt automatically when source code changes. This topic answers common questions about source code repository integration.
How do I switch the GitHub or GitLab account bound to Container Registry?
GitHub
Log on to GitHub and go to Personal settings > Applications. Click Revoke next to Aliyun Container Registry.
GitLab
Log on to GitLab and go to User Settings. Click the Access Tokens tab, then click Revoke next to the token in the Active Personal Access Tokens section.
Why does GitLab binding fail with "Failed to access the source code repository site"?
This error means Container Registry cannot reach your GitLab instance. Check the following possible causes.
Cause: Network connectivity issue
-
If you are using Container Registry Enterprise Edition to connect to an on-premises GitLab via the virtual private cloud (VPC) endpoint of your instance, verify that the VPC endpoint you entered is correct. For details, see Step 1: Manage the link.
-
If you are using Container Registry Enterprise Edition to connect to an on-premises GitLab via the public endpoint of your instance, make sure the GitLab instance is accessible from the Internet.
-
If you are using Container Registry Personal Edition to connect to an on-premises GitLab, make sure the GitLab instance is accessible from the Internet.
Cause: Incorrect binding information
Check that the GitLab URL, username, and access token are all correct.
Cause: Invalid TLS certificate
If your GitLab instance does not have a firewall, or uses an invalid self-signed TLS certificate with an incomplete certificate chain, the connection will fail. Use SSL status detection to verify your certificate.
Cause: Network timeout
If the request times out, check your network connection and try again.
Why does GitLab binding fail with "The source code repository site returns an error response"?
This error means the connection to GitLab succeeded, but the server returned an error due to configuration issues. Check the following possible causes.
Cause: Insufficient webhook permission
The account used to bind the repository must have permission to set a webhook. Verify the settings on the Integrations page of your GitLab project.
Cause: Binding information mismatch
Check that the username and repository name in your binding configuration match those in the Git repository URL exactly.