GitLab vs Google Cloud Source Repositories

Need advice about which tool to choose?Ask the StackShare community!


+ 1
Google Cloud Source Repositories

+ 1
Add tool

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


GitLab and Google Cloud Source Repositories are two popular version control systems used for managing source code. Both platforms offer similar functionalities but also have key differences that set them apart. In this document, we will explore the key differences between GitLab and Google Cloud Source Repositories.

  1. Pricing Structure: GitLab offers a range of pricing options including a free version, self-managed, and cloud-hosted plans. Google Cloud Source Repositories, on the other hand, are primarily built for use within the Google Cloud Platform and are included as part of the overall pricing structure for other services. This means that access to Google Cloud Source Repositories may require a Google Cloud Platform subscription.

  2. Integration with CI/CD: GitLab has robust features for continuous integration and deployment (CI/CD). It provides built-in CI/CD pipelines that can be easily configured to automate building, testing, and deploying applications. Google Cloud Source Repositories, although integrated with Google Cloud Build, may require additional setup and configuration for similar CI/CD workflows.

  3. Collaboration Features: GitLab is known for its strong collaboration capabilities, offering features such as merge requests, inline code commenting, and code review workflows. Google Cloud Source Repositories, while offering basic collaboration functionalities, may not have the same level of advanced collaboration features as GitLab.

  4. Access Control and Permissions: GitLab provides fine-grained access control and permissions settings, allowing users to define various roles and access levels for their repositories. Google Cloud Source Repositories have similar access control mechanisms but may have some limitations or differences in terms of permission granularity.

  5. Community and Open Source: GitLab has a large and active open-source community, with many projects and features developed collaboratively. It also allows self-hosting, contributing to the open-source spirit. Google Cloud Source Repositories, being primarily a part of the Google Cloud Platform, may not have the same level of community involvement and self-hosting options.

  6. Built-in DevOps Platform: GitLab provides an integrated platform for end-to-end DevOps processes, including version control, CI/CD, and container registry. It aims to be a one-stop solution for software development. Google Cloud Source Repositories, although integrated with other Google Cloud services, may not have the same level of built-in DevOps capabilities as GitLab.

In summary, GitLab offers a diverse and flexible pricing model, stronger collaboration features, better access control, and a more active open-source community. On the other hand, Google Cloud Source Repositories provide tighter integration with Google Cloud Platform services and a built-in ecosystem for Google Cloud users. The choice between the two would depend on specific requirements, preferences, and the existing infrastructure stack.

Decisions about GitLab and Google Cloud Source Repositories
Weverton Timoteo

Do you review your Pull/Merge Request before assigning Reviewers?

If you work in a team opening a Pull Request (or Merge Request) looks appropriate. However, have you ever thought about opening a Pull/Merge Request when working by yourself? Here's a checklist of things you can review in your own:

  • Pick the correct target branch
  • Make Drafts explicit
  • Name things properly
  • Ask help for tools
  • Remove the noise
  • Fetch necessary data
  • Understand Mergeability
  • Pass the message
  • Add screenshots
  • Be found in the future
  • Comment inline in your changes

Read the blog post for more detailed explanation for each item :D

What else do you review before asking for code review?

See more
Weverton Timoteo

Using an inclusive language is crucial for fostering a diverse culture. Git has changed the naming conventions to be more language-inclusive, and so you should change. Our development tools, like GitHub and GitLab, already supports the change.

SourceLevel deals very nicely with repositories that changed the master branch to a more appropriate word. Besides, you can use the grep linter the look for exclusive terms contained in the source code.

As the inclusive language gap may happen in other aspects of our lives, have you already thought about them?

See more
Weverton Timoteo

One of the magic tricks git performs is the ability to rewrite log history. You can do it in many ways, but git rebase -i is the one I most use. With this command, It’s possible to switch commits order, remove a commit, squash two or more commits, or edit, for instance.

It’s particularly useful to run it before opening a pull request. It allows developers to “clean up” the mess and organize commits before submitting to review. If you follow the practice 3 and 4, then the list of commits should look very similar to a task list. It should reveal the rationale you had, telling the story of how you end up with that final code.

See more
Kamaleshwar BN
Senior Software Engineer at Pulley · | 8 upvotes · 666.7K views

Out of most of the VCS solutions out there, we found Gitlab was the most feature complete with a free community edition. Their DevSecops offering is also a very robust solution. Gitlab CI/CD was quite easy to setup and the direct integration with your VCS + CI/CD is also a bonus. Out of the box integration with major cloud providers, alerting through instant messages etc. are all extremely convenient. We push our CI/CD updates to MS Teams.

See more

Gitlab as A LOT of features that GitHub and Azure DevOps are missing. Even if both GH and Azure are backed by Microsoft, GitLab being open source has a faster upgrade rate and the hosted by solution seems more appealing than anything else! Quick win: the UI is way better and the Pipeline is way easier to setup on GitLab!

See more
Nazar Atamaniuk
Shared insights

At DeployPlace we use self-hosted GitLab, we have chosen GitLab as most of us are familiar with it. We are happy with all features GitLab provides, I can’t imagine our life without integrated GitLab CI. Another important feature for us is integrated code review tool, we use it every day, we use merge requests, code reviews, branching. To be honest, most of us have GitHub accounts as well, we like to contribute in open source, and we want to be a part of the tech community, but lack of solutions from GitHub in the area of CI doesn’t let us chose it for our projects.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of GitLab
Pros of Google Cloud Source Repositories
  • 508
    Self hosted
  • 430
  • 339
    Has community edition
  • 242
    Easy setup
  • 240
    Familiar interface
  • 137
    Includes many features, including ci
  • 113
    Nice UI
  • 84
    Good integration with gitlabci
  • 57
    Simple setup
  • 34
    Has an official mobile app
  • 34
    Free private repository
  • 31
    Continuous Integration
  • 22
    Open source, great ui (like github)
  • 18
    Slack Integration
  • 15
    Full CI flow
  • 11
    Free and unlimited private git repos
  • 10
    User, group, and project access management is simple
  • 9
    All in one (Git, CI, Agile..)
  • 8
    Built-in CI
  • 8
    Intuitive UI
  • 6
    Full DevOps suite with Git
  • 6
    Both public and private Repositories
  • 5
    So easy to use
  • 5
  • 5
    Integrated Docker Registry
  • 5
    It's powerful source code management tool
  • 5
    Build/pipeline definition alongside code
  • 4
    Issue system
  • 4
  • 4
    Unlimited free repos & collaborators
  • 4
    Security and Stable
  • 4
  • 4
    It's fully integrated
  • 4
    Mattermost Chat client
  • 4
  • 3
    Great for team collaboration
  • 3
    Built-in Docker Registry
  • 3
    Low maintenance cost due omnibus-deployment
  • 3
    I like the its runners and executors feature
  • 3
    Free private repos
  • 3
    Because is the best remote host for git repositories
  • 3
    Not Microsoft Owned
  • 3
  • 2
    Groups of groups
  • 2
    Powerful software planning and maintaining tools
  • 2
    Review Apps feature
  • 2
    Kubernetes integration with GitLab CI
  • 2
    It includes everything I need, all packaged with docker
  • 2
    Multilingual interface
  • 2
    HipChat intergration
  • 2
    Powerful Continuous Integration System
  • 2
    One-click install through DigitalOcean
  • 2
    The dashboard with deployed environments
  • 2
    Native CI
  • 2
    Many private repo
  • 2
    Kubernetes Integration
  • 2
    Published IP list for whitelisting (gl-infra#434)
  • 2
  • 2
  • 1
    Supports Radius/Ldap & Browser Code Edits
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Cons of GitLab
    Cons of Google Cloud Source Repositories
    • 28
      Slow ui performance
    • 8
      Introduce breaking bugs every release
    • 6
      Insecure (no published IP list for whitelisting)
    • 2
      Built-in Docker Registry
    • 1
      Review Apps feature
      Be the first to leave a con

      Sign up to add or upvote consMake informed product decisions

      What is GitLab?

      GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.

      What is Google Cloud Source Repositories?

      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.

      Need advice about which tool to choose?Ask the StackShare community!

      What companies use GitLab?
      What companies use Google Cloud Source Repositories?
      See which teams inside your own company are using GitLab or Google Cloud Source Repositories.
      Sign up for StackShare EnterpriseLearn More

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with GitLab?
      What tools integrate with Google Cloud Source Repositories?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      Blog Posts

      What are some alternatives to GitLab and Google Cloud Source Repositories?
      GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
      Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.
      In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
      The goal of this project is to make the easiest, fastest and most painless way to set up a self-hosted Git service. With Go, this can be done in independent binary distribution across ALL platforms that Go supports, including Linux, Mac OS X, and Windows.
      Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
      See all alternatives