Comment by zdw

Comment by zdw 3 days ago

7 replies

If you want even more minimal, Gerrit is structured as a Java app with no external dependencies like databases, and stores all it's configuration and runtime information on the filesystem, mostly as data structures in the git repos.

Shared filesystems is all you need to scale/replicate it, and it also makes the backup process quite simple.

hk1337 3 days ago

I might be one of the few that is intrigued by this being that it’s Java but this looks really neat. Does it do git repositories like gitea, GitHub, etc, or is it more of a project management site for the repositories? They describe it as “code review”, so I wasn’t sure.

I’m a little put off on the google connection but it seems like it could run rather independently.

  • arccy 3 days ago

    It necessarily hosts a git server (using jgit), but the primary interface is as a code review tool.

    even browsing the git repos it hosts uses an embedded version of another tool (gitiles).

    https://gerrithub.io/ is a public instance

  • zdw 3 days ago

    It's hyper-focused on code review and CI integration, which it does really well.

    It's not focused on all the other stuff that people think of in code forges (hosting the README in a pretty way, arbitrary page hosting, wiki, bug tracking, etc.) but can be integrated with 3rd party implementations of those fairly trivially.

  • dsassoli09 2 days ago

    > I’m a little put off on the google connection but it seems like it could run rather independently.

    Yeah, its actually a really healthy open-source project, google contributes usually around 40% of the code, but you have other companies like GerritForge(disclaimer, I work here), Nvidia, SAP, Qualcomm, Wikimedia foundation, all contributing heavily to it.

Kwpolska 3 days ago

The deployment may be simple, but at the same time, the Gerrit code review workflow is terrible.

  • dsassoli09 2 days ago

    Coming from Github myself, I cannot imagine going back to it after using Gerrit for even just a few days.

    The workflow in Gerrit really makes a lot of sense, unfortunately its the workflow in GitHub that has screwed up everyone's idea of what code review should look like[1], even by one of GitHub's co-founder own's admission.

    [1] https://medium.com/@danielesassoli/how-github-taught-the-wor...

  • zdw 3 days ago

    I personally find the rebase and stacking commit focused method of integration that Gerrit uses to be easier and cleaner than PR's in GitHub.

    Having done CI integrations with both, Gerrit's APIs send pre- and post-merge events through the same channel, instead of needing multiple separate listeners like GitHub.