General questions about Managed Service for GitLab
-
How to migrate data from GitLab to Managed Service for GitLab?
-
Is there support for GitLab integration with Yandex Tracker?
-
Why cannot I push changes to the Managed Service for GitLab repository?
-
I get
500 Internal Server Errorwhen opening an instance. What could be the problem? -
How do I set up an alert that triggers when a certain percentage of disk space is used?
-
Can I change instance type or disk size after the instance has been created?
-
What should I do if I cannot connect to the system hook on
localhost?
What are the advantages of Managed Service for GitLab over a GitLab Community Edition custom installation?
The main advantage of Managed Service for GitLab is that it reduces the installation and administration costs of GitLab. In addition, Managed Service for GitLab adds functionality not found in the Community Edition
How to migrate data from GitLab to Managed Service for GitLab?
You can migrate data from a GitLab custom installation to Managed Service for GitLab. Learn how to do this in this guide. Before you begin, see how to run migration.
You cannot migrate data from GitLab.com to Managed Service for GitLab: migration is only available for GitLab installed on a server or local computer (self-managed GitLab).
Can I integrate GitLab authentication providers?
Yes, you can. To do this, configure OmniAuth.
Can I use Yandex ID or Yandex 360 for authentication?
Yes, you can. To do this, add a provider of the Yandex ID type to OmniAuth and configure its parameters.
Is there GitLab integration with Yandex Tracker?
Yes, there is. For the integration settings, see Integration with Yandex Tracker
Why cannot I push changes to the Managed Service for GitLab repository?
Error messages:
You are not allowed to push code to this project.
You are not allowed to push code to protected branches on this project.
To push changes to the Managed Service for GitLab repository, assign
- To protected branches (e.g.,
master):MaintainerorOwner. - To unprotected branches:
Developer,Maintainer, orOwner.
Users with the Guest and Reporter roles cannot push changes.
For more information about roles, see the GitLab documentation
I get 500 Internal Server Error when trying to open the instance. What could be the problem?
The instance disk space may be full. You can increase the instance disk space yourself.
For details, see Cleaning up full instance disk space.
How can I clear pipeline logs to free up disk space?
You cannot delete the logs separately. However, you delete them by deleting irrelevant pipelines.
Where can I track my disk space usage?
You can track your disk space:
- In the management console using instance status monitoring tools.
- In Yandex Monitoring, where you can set up alerts based on specified metrics.
How do I set up an alert that triggers as soon as a certain percentage of disk space has been used up?
See Setting up alerts in Monitoring for Managed Service for GitLab.
Why cannot I create backups?
If backup creation fails (Failed status), configure a separate security group and link it to the GitLab instance.
Can I change instance type or disk size after the instance has been created?
Yes, you can upgrade your instance to a higher performance type and increase its disk size. However, you cannot reduce instance disk size or switch to a lower performance type. For more information, see Editing instance settings.
What should I do if I cannot connect to the system hook on localhost?
If you cannot connect to the system hook, use the 127.0.0.1 IP address instead of localhost:
- In the system hook settings (Admin area → System Hooks), change the URL value to
http://127.0.0.1:24080/default. - In the GitLab settings that allow sending messages to the local network (Admin area → Settings → Network → Expand outbound requests, CIDR input field), add
http://127.0.0.1:24080to the list of IP addresses and domain names.