Bitbucket Server vs RhodeCode

It's easy to create pull requests through the different view options and commenting. Stash also offers code reviews via pull requests, leading to better code quality.

Stash uses JIRA for issue tracking and integrate out-of-the-box with Bamboo and Hitchat. Furthermore, it has many third party integrations and comprehensive API points for custom tools and integration.

Stash installation is very easy and there are install wizards for Windows, Linux and OSX. There are also a lot of tutorials and guides that cover the installation process and more.

Stash is built with focus on enterprise teams, as such it can scale up to 5000 users on a single instance, it is flexible enough to deploy to multiple OS and has multiple backing stores and database options.

Stash is backed and developed by Atlassian, an established and world-class software company with a great history of customer support.

Stash has a permissions system that has 4 levels that go down to branch level.

1. Global Permissions: Decide who can log in, who the system admin is, etc...
2. Project Permissions: Read, write, and admin permissions at the project level.
3. Repository Permissions: Read, write, and admin permissions on a repository level.
4. Branch Permissions: Access and write(push) on a branch level.

In Stash, pull requests are visible to all team members, but they can only be approved for merging by a limited number of globally set reviewers.

Works fully on Linux and with limitations on Windows and OS X. It also has installers that will make the installation easy for each of them.

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.

RhodeCode supports Mercurial, Git and Subversion in a unified way that allows you to do code-reviews and other stuff on each of them.

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.

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.

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.

RhodeCode has auth plugins, now supported include: LDAP, LDAP with user groups, TOKEN, Container auth, PAM

Files can be added, modified and deleted from the web interface, including adding directories, and uploading files.

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.

The builtin header auth can delegate authentication to other existing systems for further validation chain.