GitLab

GitLab
File:Gitlab-logo.svg.svg
Backup and Restore Cheat Sheet Failover Gitlab Runner Gitlab Runner/Cloud Runners Gitlab Runner/Plattform Evaluation Gitlab Runner/Security Evaluation Gitlab Runner/Shared Runners Gitlab Runner/Trusted Runners Monitoring Phabricator integration Replica Stewardship Test Instance Upgrade External resources: Production GitLab GitLab docs GitLab in MediaWiki GitLab in Phabricator

This page contains SRE related topics for GitLab. For GitLab application specific information, please see https://www.mediawiki.org/wiki/GitLab (under Implementation).

GitLab is reachable at https://gitlab.wikimedia.org/. We run multiple instances of GitLab:

• gitlab1001 runs production GitLab serving https://gitlab.wikimedia.org/
• gitlab2001 runs a passive GitLab replica serving https://gitlab-replica.wikimedia.org/ (WIP)
• gitlab-ansible-test in WMCS gitlab-test project
• gitlab in WMCS gitlab-test project

GitLab instances

gitlab1001 and gitlab2001 are setup using puppet and Ansible. The base configuration currently lives in profile::gitlab. Additional GitLab specific configuration comes from gitlab-ansible. Its planned to migrate all of the logic to puppet and drop Ansible (see T283076). GitLab is installed as a Omnibus installation on all instances. So all GitLab components are installed using the official packages and are executed on a single host. The reasons for this setup can be found in the Initialization docs in Mediawiki.

GitLab login is implemented with SSO using the CAS/SSO. So users will be redirected to idp.wikimedia.org to login to the SSO portal. Groups ops, wmf or nda are needed to access GitLab currently.

GitLab runners

For our current and future runner setups, see GitLab/Gitlab Runner.