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.
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 heavy. Since i don't use that many features i use forgejo and it does everything i need