GitLab – do you host one? Or use the cloud?

4 points by roscas 8mo ago ↗ HN

I would like to know what are your experiences with GitLab, either hosted by yourself or using the cloud.

We are using Azure DevOps now but might go on the Gitlab path, so there is need to convert all pipelines and more.

Just put it on a podman container on a Rocky server but I find it 'heavy' on the cpu and ram.

Thanks.

6 comments

[ 3.0 ms ] story [ 21.7 ms ] thread

stop50 8mo ago ↗

Gitlab is heavy. Since i don't use that many features i use forgejo and it does everything i need

roscas 8mo ago ↗

Thanks, like Codeberg. I will look at it too.

nacozarina 8mo ago ↗

I’ve had positive experience with self-hosted gitlab, always with containers. Go thru full backup, recovery, move-server tests with your config, make sure you understand your setup. (Like any recovery plan, you have to practice it.)

I liked having dedicated ticketing and release management By And For The Devs, that is separate from comparable systems for PMO, OPs, other stakeholders. Can always track stuff by referencing each others tickets, whether in jira, redmine, et al. I always moved to Gitlab from Jenkins for ci/cd, always felt it was an upgrade. YMMV.

roscas 8mo ago ↗

We are not using Jenkins now, but we still use Mantis and a few years ago starting to move to Azure DevOps. Now someone want to leave Azure.

nik736 8mo ago ↗

GitLab is very very heavy with a lot of bloat and sadly still a bad UI/UX. I prefer Gitea for its simplicity. Gitea Actions are similar to Github Actions and they work great.

roscas 8mo ago ↗

Thanks and I will look at Gitea also. But that will not be my decision.