Services/Gitlab
Gitlab
The FB3 hosts Gitlab under the following URL:
Any FB3 user with an Uni-Account can log in (via the LDAP tab). Upon the first login, a GitLab account is automatically created and can only be found afterward (e.g. for inviting to a project).
Each person can create up to 100 projects by default. If this is not sufficient, the limit can be increased. Please send an email to service
informatik.uni-bremen.de or create a ticket in the GitLab project.
To access repositories managed by GitLab via SSH, an SSH key pair is required. Public keys can be added in GitLab by clicking on your profile picture in the top left, then selecting "Edit Profile" or "Preferences," and then clicking on "SSH Keys" in the navigation bar on the left.
The RSA fingerprint for the server is
- MD5:9b:1e:c6:c6:78:69:14:be:e9:5b:e7:24:09:32:78:47
- SHA256:nVTL/k5lSm4Kic3VfN9np76syi2PTVqPsuTmlDuvq5M
The ED25519 fingerprint for the server is
- MD5:71:a5:06:04:aa:b2:27:96:45:ac:69:52:aa:8c:6b:a4
- SHA256:iJcPCKgka3CYBjml2tDYMasJ/Crqw64Bg9V1WoboC8E
To ensure consistent backups, GitLab is unavailable every day from around 23:00 for a few minutes.
For questions or issues with GitLab, please send an email to serviceinformatik.uni-bremen.de or create a ticket in the GitLab project.
Continuous Integration and Delivery (CI/CD)
Gitlab has an integrated service for Continuous Integration und Delivery (CI/CD) that can e.g. be used for automated testing.
External cooperation partners
For external cooperation partners, GitLab accounts can be created if needed. Please send an email with the name, desired username, and email address of the person to serviceinformatik.uni-bremen.de. Note: the username must contain a dot ('.') to avoid naming conflicts with Uni-Accounts (e.g., use otto.mustermann or o.mustermann). For members of the University of Bremen from other departments, the Uni-Account can usually be activated for the use of FB3 services. See the Accounts page for more information.
GitLab accounts for externals, which are not linked to an Uni-Account, cannot create their own projects or groups.
Deletion of Gitlab-Accounts
Once an Uni-Account loses access to FB3 services, the associated GitLab account is automatically locked. If the account regains access to FB3 services at a later time, the associated GitLab account will be automatically unlocked upon the next login. Locked GitLab accounts that are linked to an Uni-Account will be retained until the associated Uni-Account is deleted, at which point they will also be deleted.
External accounts are automatically deactivated after one year of inactivity, and their owners are notified via email. The respective account can be reactivated independently by logging into GitLab. If an external account remains deactivated for more than 30 days, it will be automatically deleted.
All personal projects (i.e. projects in the account's namespace) will be deleted along with the account. All contributions, such as commits, comments, issues, etc., will be transferred to the "Ghost" account after deletion. See also the GitLab documentation on this topic.
If the respective account is the sole owner of a group, the group will be transferred to an arbitrary account with the next higher access rights. If the respective account is the only member of the group, the group will be deleted. If this is not desired, it should be ensured in advance that a successor owner is appointed (or the group is deleted).
Gitlab accounts can also be deleted independently. This can be done by clicking on your profile picture in the top left, then selecting "Edit Profile" or "Preferences" and then clicking on "Account" under "User settings" on the left.