We are changing our system. We settled on git (but are open for alternatives) as long as we can selfhost it on our own machines.

Specs

Must have

  • hosted on promise
  • reliabile
  • unlikely to be discontinued in the next >5 years
  • for a group of at least 20 people

Plus

  • gui / windows integration
  • pezhore@lemmy.mlEnglish
    7·
    3 months ago

    I’ll come out with an anti-recommendation: Don’t do GitLab.

    They used to be quite good, but lately (as in the past two years or so) they’ve been putting things behind a licensing paywall.

    Now if your company wants to pay for GitLab, then maybe consider it? But I’d probably look at some of the other options people have mentioned in this thread.

    • theroff@aussie.zoneEnglish
      5·
      3 months ago

      The company behind GitLab is seeking buyout offers, so make of that what you will.

      My employer uses GitLab CE and it’s pretty good, and it is FOSS. The EE version is “open core” so not really FOSS.

      If I were starting from scratch I’d be looking into Gitea/Forgejo as well.

    • swooosh@lemmy.worldOPEnglish
      3·
      3 months ago

      I’m all for foss but foss shall not be a reason to stay behind. We’ve got enough money to pay for it. We just can’t host it anywhere. We have to selfhost it. If there’s a good reason to use gitlab over forgejo, we will use gitlab.

      • poVoq@slrpnk.netEnglish
        6·
        3 months ago

        Gitlab’s main advantage is the tight integration with CI/CD and a web based IDE. But it has some annoying limitations in the non-enterprise version.

        Forgejo is great, but it comes with only community support.

        You can get commercial support from the Gitea project (from which Forgejo forked off), but if that is something important for you, Gitlab has probably also better commercial support structures in place.

        • swooosh@lemmy.worldOPEnglish
          3·
          3 months ago

          Money is not an issue. We’re happy to pay for everything. I’ll talk to the others in the next round to get to a conclusion.

          • pezhore@lemmy.mlEnglish
            2·
            3 months ago

            Yeah, for the integrated CI/CD, give GitLab a shot - it saves on spinning up a Jenkins or ConcourseCI server.

            CI/CD can be useful for triggering automation after merge requests are approved, building infrastructure from code, etc.