When comparing RhodeCode vs Google Cloud Source Repositories, the Slant community recommends RhodeCode for most people. In the question“What are the best hosted version control services?” RhodeCode is ranked 6th while Google Cloud Source Repositories is ranked 8th. The most important reason people chose RhodeCode is:
It's open source and it can be installed on your own machine, which gives high security and isolated environment for the codes. Whole application installation is super easy and independent from the Linux distribution.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro High security
It's open source and it can be installed on your own machine, which gives high security and isolated environment for the codes. Whole application installation is super easy and independent from the Linux distribution.
Pro Supports 3 major version control systems
RhodeCode supports Mercurial, Git and Subversion in a unified way that allows you to do code-reviews and other stuff on each of them.
Pro Centralized user management
User management is centralized around administrators which can give granular permissions to individual users or user groups/. These permissions can be related to allowing contributions, editing, or simply giving read-only access to users.
Pro Powerful and flexible code review
Code reviews can be done via Pull Requests, or simply commit-by-commit. There are voting rules, random reviewers pools, and smart comment invalidation logic. Pull requests are also versioned so it's easy to review partial changes after the author has updated his code.
When you create a Pull-request you can add set of reviewers. They all have to vote and approve the PR. There's some flexibility on how the voting is accepted, it can be majority wins, or all-agree. Good practice is to add BOT accounts like jenkins, that also will vote on the review, based on for example tests run, and can forbid a merge because of a negative vote. In addition users can leave special type of comments that will also prevent merges, aka TODO notes. Once TODOs are resolved a Pull Request can be merged.
Pro Free and Open Source
RhodeCode CE (Community Edition ) is free and open source. Enterprise Edition (EE) adds premium support, corporate authentication. and tool integrations on top of the RhodeCode CE.
Pro Integrates fully with LDAP/AD and others
RhodeCode has auth plugins, now supported include: LDAP, LDAP with user groups, TOKEN, Container auth, PAM
Pro Online editing with preview
Files can be added, modified and deleted from the web interface, including adding directories, and uploading files.
Pro Best in class permission system
RhodeCode have the most advanced Permission system on the market, allowing things like permission inheritance, permission delegation. All comes in a format that doesn't get hard to manage at scale.
Pro Header authentication plugin allows auth delegation to 3rd party systems
The builtin header auth can delegate authentication to other existing systems for further validation chain.
Pro Free tier
Cloud Source Repositories is free for up to 5 project-users per billing account. The free tier comes with up to 50GB free storage total and 50GB free egress per month.
Pro Excellent security
Everything is stored encrypted in Google's datacenters. You can give fine grained control to other Google accounts and collaborate.
Pro Integrated with other Google Cloud Platform services
Trigger deployments or create custom integrations using Google Cloud Pub/Sub, deploy directly to App Engine or Cloud Functions, and use Cloud Build for CI. Check out code securely (Service Accounts) from your Cloud Compute instances or Container Engine images. View logs in Stackdriver.
Cons
Con Hard to maintain and upgrade
The documentation is not very clear and it's hard to troubleshoot if there is a failure.
Con Markdown styling is not as good as GitHub or GitLab
Your README files will not render as nicely as GitHub and GitLab, which may irritate you if you're migrating your repos with nicely-formatted docs.
Con No inline editing
Unlike some other popular repositories, there is no way to edit inline directly from the source browser. Although, you can easily open up a Theia-based IDE in the browser to edit and run your code by clicking the "Open in Cloud Shell" button. You will still have to commit your changes from the Cloud Shell command line, though.
Con Must set-up billing account
For all Google Cloud Platform projects you must enable Billing. This isn't uncommon for cloud hosting providers but it still could be considered a CON.