| > On the other hand: there is not much of an alternative to GitLab. Honestly, in larger organizations self-hosted GitLab is still one of the better options. It has lots of features and gets the basics right (though not all are excellent) - you get code review, CI/CD, even functionality for issue tracking, Wikis and much more. You might use Jira or Atlassian for some of those, or maybe something more tailored and optimized for your workflows in smaller orgs, but GitLab still offers you options for most of the things you might want to do (even some monitoring and feature flags). As long as you can keep up with resource requirements and updates, as well as configuration, you aren't likely to get fired for picking it and you'll be able to succeed and ship projects while using it, if self-hosting is a must/preferable. > Atlassian self hosting is no more. Maybe Gitea + anything for CI/CD? That said, for my personal needs, I migrated away from GitLab and run Gitea (for the code), Drone (for CI) and Sonatype Nexus (for container images, libraries etc.): https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-... In my case, dealing with updates is a bit easier now and breakages don't affect the whole solution (since previously I ran Omnibus GitLab for my own needs, which made launching it easier, at the expense of more coupling) and the total footprint would be much lower, if only Nexus wouldn't love to gobble that much RAM. Sometimes integrating a bunch of specialized solutions is also a valid approach, especially because in my case container image cleanup in GitLab was a bit of a mess and while Nexus still has its problems (e.g. skipped deletion of old container images when they have multiple tags), it's a bit better and gives you more control. Gitea is great, though and should work with most of the popular CI solutions as well - whether you want to run Drone, Jenkins, or anything else. |