• GitLab at KIT

  • The SCC operates the GitLab platform for KIT at https://gitlab.kit.edu. The SCC provides the service in cluster mode for up to 3000 concurrent users starting in early July.


In software development, "git" has become the de facto standard as a tool for decentralized version management in recent years. Based on this, GitLab offers a web application for project management, documentation, bug tracking, build creation and deployment including continuous integration.

Possible application scenarios at KIT include courses on programming as well as software development in research (also RSE). In addition, the platform is also suitable for managing text-based documents, e.g. in the markup languages like LaTeX or Markdown.

Included services

Students, employees, and holders of guest and partner accounts (GuP login) of KIT can access the instance at https://gitlab.kit.edu. Authentication is done via "FeLS - Federated Login Service".

Within the scope of the basic service, each user can set up up to 50 projects with 1 GB quota each. If this is not sufficient, for example because many small repositories with GIT submodules are needed, the quota can be increased on request.

Services not included

The runners required to use GitLab CI are not provided by SCC. If required, resources in the form of virtual machines can be purchased from SCC for this purpose.

The GitLab Pages feature is disabled. For hosting websites, the SCC offers "Virtual Web Servers". A service, which can be provisioned using GitLab CI in a similar way as GitLab Pages (see www.scc.kit.edu/dienste/webserver.php).

For licensing reasons, external users can only collaborate on projects of KIT persons, but cannot initiate their own projects.

Deprovisioning rules

To ensure an economic use of the licenses, the following deprovisioning rules apply: Accounts that have not been logged in for half a year will be blocked. For unblocking a mail to git@scc.kit.edu is necessary. A blocking for other reasons (e.g. leaving KIT) remains unaffected.

After another half a year, locked accounts including their projects will be removed. Data in other projects (e.g. comments in issues) remain contentwise, but are inherited to a "ghost user".