GitLab vs Perforce

Overview

GitLab

Stacks63.4K

Followers54.5K

Votes2.5K

GitHub Stars0

Forks0

Perforce

Stacks83

Followers113

Votes9

GitLab vs Perforce: What are the differences?

Introduction

GitLab and Perforce are both version control systems used by software development teams to manage and track changes to their codebase. While they share similarities in their basic functionality, there are key differences that set them apart.

Code Ownership: One major difference between GitLab and Perforce is their approach to code ownership. GitLab follows a distributed model, where each developer has their own repository and can work independently. On the other hand, Perforce uses a centralized model, where all code is stored in a central repository and developers need to check out files before making changes.
Branching Strategy: GitLab offers a more flexible and powerful branching strategy compared to Perforce. GitLab uses a lightweight branching model, allowing developers to easily create and merge branches for different features or bug fixes. Perforce, on the other hand, uses a more traditional branching approach, which can be complex and time-consuming for large projects.
Integration and Extensibility: GitLab has a strong focus on integration and extensibility. It provides a wide range of integrations with other tools commonly used in software development, such as issue tracking systems, continuous integration/delivery platforms, and chatops. Perforce, while offering some integrations, may not have the same level of extensibility and integration options as GitLab.
Open Source: GitLab is an open-source platform, which means that the source code is freely available to the public and can be modified and distributed by anyone. This openness allows for greater community collaboration and contributions. Perforce, on the other hand, is a proprietary software that is not open source.
Licensing: Another difference between GitLab and Perforce is their licensing model. GitLab offers both a free community edition and a paid enterprise edition. The community edition provides most of the basic functionality needed for small to medium-sized teams, while the enterprise edition offers additional features and support for larger organizations. Perforce, on the other hand, has a commercial licensing model, where users need to purchase licenses to use the software.
Scalability: GitLab is known for its scalability and can handle large codebases and high volumes of traffic efficiently. It has features like scaling horizontally by adding more servers and using load balancers to distribute the workload. Perforce, while also scalable, may require additional configuration and setup to handle large-scale projects.

In summary, GitLab and Perforce differ in their approach to code ownership, branching strategy, integration and extensibility, open-source nature, licensing model, and scalability capabilities.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on GitLab, Perforce

Anonymous

May 25, 2020

Decided

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 gitlab.com solution seems more appealing than anything else! Quick win: the UI is way better and the Pipeline is way easier to setup on GitLab!

624k views624k

Comments

Phillip

Developer at Coach Align

Mar 18, 2021

Decided

Both of us are far more familiar with GitHub than Gitlab, and so for our first big project together decided to go with what we know here instead of figuring out something new (there are so many new things we need to figure out, might as well reduce the number of optionally new things, lol). We aren't currently taking advantage of GitHub Actions or very many other built-in features (besides Dependabot) but luckily it integrates very well with the other services we're using.

409k views409k

Comments

Weverton

CTO at SourceLevel

Jul 28, 2020

Review

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?

944k views944k

Comments

Detailed Comparison

GitLab	Perforce
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.	Visibility, access control, workflow and code management for Git environments. Flexibility of collaborating on the same codebase and code reviews using any combination of Perforce and Git workflows and tools without compromise.
Manage git repositories with fine grained access controls that keep your code secure;Perform code reviews and enhance collaboration with merge requests;Each project can also have an issue tracker and a wiki;Used by more than 100,000 organizations, GitLab is the most popular solution to manage git repositories on-premises;Completely free and open source (MIT Expat license);Powered by Ruby on Rails	Version Control; Application Lifecycle Management; Static Code Analysis for C, C++, C#, and Java; Codeless Selenium Test Automation; Open Source Support; Enterprise PHP Development
Statistics
GitHub Stars 0	GitHub Stars -
GitHub Forks 0	GitHub Forks -
Stacks 63.4K	Stacks 83
Followers 54.5K	Followers 113
Votes 2.5K	Votes 9
Pros & Cons
Pros 508 Self hosted 431 Free 339 Has community edition 242 Easy setup 240 Familiar interface Cons 28 Slow ui performance 9 Introduce breaking bugs every release 6 Insecure (no published IP list for whitelisting) 2 Built-in Docker Registry 1 Review Apps feature	Pros 3 Powerful 3 Great for Enterprise level use 2 Robust 1 Scalable
Integrations
No integrations available	Git

What are some alternatives to GitLab, Perforce?

GitHub

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

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.

RhodeCode

RhodeCode provides centralized control over distributed code repositories. Developers get code review tools and custom APIs that work in Mercurial, Git & SVN. Firms get unified security and user control so that their CTOs can sleep at night

AWS CodeCommit

CodeCommit eliminates the need to operate your own source control system or worry about scaling its infrastructure. You can use CodeCommit to securely store anything from source code to binaries, and it works seamlessly with your existing Git tools.

Gogs

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.

Gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD. It published under the MIT license.

Upsource

Upsource summarizes recent changes in your repository, showing commit messages, authors, quick diffs, links to detailed diff views and associated code reviews. A commit graph helps visualize the history of commits, branches and merges in your repository.

Beanstalk

A single process to commit code, review with the team, and deploy the final result to your customers.

GitBucket

GitBucket provides a Github-like UI and features such as Git repository hosting via HTTP and SSH, repository viewer, issues, wiki and pull request.

BinTray

Bintray offers developers the fastest way to publish and consume OSS software releases. With Bintray's full self-service platform developers have full control over their published software and how it is distributed to the world.

Related Comparisons

GitLab vs Perforce: What are the differences?

Introduction

Code Ownership: One major difference between GitLab and Perforce is their approach to code ownership. GitLab follows a distributed model, where each developer has their own repository and can work independently. On the other hand, Perforce uses a centralized model, where all code is stored in a central repository and developers need to check out files before making changes.
Branching Strategy: GitLab offers a more flexible and powerful branching strategy compared to Perforce. GitLab uses a lightweight branching model, allowing developers to easily create and merge branches for different features or bug fixes. Perforce, on the other hand, uses a more traditional branching approach, which can be complex and time-consuming for large projects.
Integration and Extensibility: GitLab has a strong focus on integration and extensibility. It provides a wide range of integrations with other tools commonly used in software development, such as issue tracking systems, continuous integration/delivery platforms, and chatops. Perforce, while offering some integrations, may not have the same level of extensibility and integration options as GitLab.
Open Source: GitLab is an open-source platform, which means that the source code is freely available to the public and can be modified and distributed by anyone. This openness allows for greater community collaboration and contributions. Perforce, on the other hand, is a proprietary software that is not open source.
Licensing: Another difference between GitLab and Perforce is their licensing model. GitLab offers both a free community edition and a paid enterprise edition. The community edition provides most of the basic functionality needed for small to medium-sized teams, while the enterprise edition offers additional features and support for larger organizations. Perforce, on the other hand, has a commercial licensing model, where users need to purchase licenses to use the software.
Scalability: GitLab is known for its scalability and can handle large codebases and high volumes of traffic efficiently. It has features like scaling horizontally by adding more servers and using load balancers to distribute the workload. Perforce, while also scalable, may require additional configuration and setup to handle large-scale projects.

In summary, GitLab and Perforce differ in their approach to code ownership, branching strategy, integration and extensibility, open-source nature, licensing model, and scalability capabilities.

GitLab vs Perforce

Overview

GitLab vs Perforce: What are the differences?