@@ -136,3 +136,33 @@ GitLab comes with a flexible CI/CD system which can be used to run tests and/or
...
@@ -136,3 +136,33 @@ GitLab comes with a flexible CI/CD system which can be used to run tests and/or
In the specific case of codecov.io, yes. The [codecov documentation](https://docs.codecov.io/docs/link-service-provider#section-gitlab-ceee) includes information on integrating with self-hosted GitLab instances.
In the specific case of codecov.io, yes. The [codecov documentation](https://docs.codecov.io/docs/link-service-provider#section-gitlab-ceee) includes information on integrating with self-hosted GitLab instances.
For other cloud-hosted CI tools you will need to check the documentation for that tool. Our self-hosted GitLab instance is often called "GitLab CE/EE" to distinguish it from the cloud-hosted gitlab.com.
For other cloud-hosted CI tools you will need to check the documentation for that tool. Our self-hosted GitLab instance is often called "GitLab CE/EE" to distinguish it from the cloud-hosted gitlab.com.
### If the service does not become chest funded, what will happen?
Ultimately, we would have to close the service. We do not intend to do this overnight. There will be advance warning and time to migrate to a cloud-hosted service or, if the intention is to deploy a different service, to the new service.
### Will there be a migration step between "alpha" and "beta" stages?
We do not intend there to be service disruption between the alpha and beta phases. Those labels are used for project management purposes primarily. We intend the service to remain the same instance if we transition except that the label at the top will change.
### Will the GitLab service replace git.uis.cam.ac.uk?
The intention is for GitLab to replace git.uis.cam.ac.uk. There is no proposed timescale for this.
### What about GitHub Enterprise?
A cross-institution group were tasked with investigating git repository hosting solutions. GitHub Enterprise was, at that time, unable to make a repository entirely public which was seen as an essential requirement for a University service. This was not the only downside but it was the most significant.
### Are there project management tools?
There are many project management tools provided in our GitLab instance. [Information on them](https://gitlab.developers.cam.ac.uk/help#plan) is available on the help page.
We do not currently offer any user support for the tools. We are interested in gathering feedback on their utility.
### Can I use GitLab as a service desk frontend?
At the moment, we do not support creating issues via email or the associated [service desk feature](https://gitlab.developers.cam.ac.uk/help/user/project/service_desk.md). This is for technical reasons related to University email provision and may be surmountable. We are keen to know if this feature is a priority for users.
### How do I migrate robot users?
Robot users which require read-only access to a repository may use a [deploy key](https://gitlab.developers.cam.ac.uk/help/ssh/README.md#deploy-keys). Robot users which interact directly with the GitLab API may need to have a robot account created. We can do this on a case-by-case basis. [Open an issue](https://gitlab.developers.cam.ac.uk/uis/devops/devhub/docs/issues/new) if you believe you need a true robot user.
