In the Hogeschool van Amsterdam HBO-ICT education department we’ve been running Gitlab for almost 10 years now. Currently 15789 projects, 1350 groups and 3121 users that come every year and leave with a BSc in 4 years (in the happy scenario).
The main reason to start using the ultimate (self hosted) version was to be able to limit the sizes of the projects so that machine learning students learn to not push the entire dataset into their repo.
The usage of gitlab is growing and since 2 years we have 2 shared docker runners to accomodate the CI/CD chain. And some users love the gitlab pages now we got that working.
And the integration with our MSTeams environment is fun: every commit is a Teams message in a private teachers Teams channel.
The LDAP integration is great too: students who leave the school are automagically “blocked” by a gitlab process that checks LDAP accounts. Once a year these are deleted from the system to keep the number of users small (under 5000). The python gitlab api tools are very helpful with that. So many things happening with gitlab it is hard to keep up.
Our current issue is about authentication: instead of reading passwords we should be using SAML2 ( SURFconext IdP Dashboard ) single sign-on to log in. But can we enable SAML2 and still be able to automatically block expired LDAP users? No hurry, just asking.
Greetings from Amsterdam Univerity of Applied Sciences,
Jan Derriks, CS lecturer and gitlab maintainer.