Gitolite vs Google Cloud Source Repositories

Gitolite vs Google Cloud Source Repositories: What are the differences?

Developers describe Gitolite as "Setup git hosting on a central server, with fine-grained access control". Gitolite allows you to setup git hosting on a central server, with fine-grained access control and many more powerful features. Gitolite is an access control layer on top of git. On the other hand, Google Cloud Source Repositories is detailed as "A single place for your team to store, manage, and track code". Collaborate easily and securely manage your code on a fully featured, scalable, private Git repository. Extend your Git workflow by connecting to other GCP tools, including Cloud Build, App Engine, Stackdriver, and Cloud Pub/Sub. Get access to fast, indexed powerful code search across all your owned repositories to save time.

Gitolite and Google Cloud Source Repositories can be primarily classified as "Code Collaboration & Version Control" tools.

Some of the features offered by Gitolite are:

• Use a single unix user ("real" user) on the server.
• Provide access to many gitolite users: they are not "real" users, so they do not get shell access.
• Control access to many git repositories: read access controlled at the repo level, and write access controlled at the branch/tag/file/directory level, including who can rewind, create, and delete branches/tags.

On the other hand, Google Cloud Source Repositories provides the following key features:

• Unlimited private Git repositories
• Deploy directly from Cloud Source Repositories
• Automatically build and test your source code

Gitolite is an open source tool with 7.45K GitHub stars and 960 GitHub forks. Here's a link to Gitolite's open source repository on GitHub.