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.
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.
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.
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.
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.
Thanks and I will look at Gitea also. But that will not be my decision.
Gitlab is heavy. Since i don't use that many features i use forgejo and it does everything i need
Thanks, like Codeberg. I will look at it too.