TrustRadius Insights for GitLab are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Cloud-Based UI and Git Integration: Users have praised the cloud-based UI of GitLab for supporting Git version control, allowing local checkout, and enabling multiple developers to work simultaneously in one file. The reduction of code conflicts and enhanced collaboration are highlighted benefits of this feature.
Integration Features: Reviewers highly value the integration of GitLab with version control, code review, and project management features. They find it easy to configure GitLab runners for running tests and defining permissions using Terraform, which streamlines their development processes effectively.
CI/CD Capabilities: Users find the CI/CD pipelines, merge requests, and open-source nature of GitLab beneficial for their development workflows. They appreciate the platform's integrations with other tools such as Jira, Azure DevOps, and Toad. Additionally, they praise its security features for ensuring a safe software deployment environment.
Gitlab is currently used across our company predominantly by our technical staff as our go-to version control manager, CI-CD pipeline and developer wiki tool for internal and external projects.
Pros
Version control
Open source
Issue tracking
Cons
Slightly difficult learning curve for non-technical staff to navigate through the relevant pages in projects
No ability to fully customise permissions
Issue tracking is not the most user friendly
Likelihood to Recommend
Gitlab is suitable for projects with a limited budget and where there are technical staff available to drive implementation and set up (particularly where CI-CD is required). Whilst there are many integrations with Gitlab, they remain very technical and not very accessible by management and other non-technical team members. It is also not the most user-friendly issue tracking tool and does not contain as many features as other alternatives in the market
We use Gitlab as a way to backup, host, and distribute source code via Git version control. It is used across our entire organization, but only about 80% of our Git repositories are hosted on Gitlab (the rest are on GitHub). We chose Gitlab for hosting the majority of our repositories because it allows us to keep an unlimited number of these repositories private for free. This is a paid feature of its major competitor, GitHub.
Pros
Free unlimited private repositories. I'm not aware of another hosted Git platform that offers this.
Gitlab CI has first-class support for continuous integration features. This makes it easy to seamlessly integrate tests, deployments, and other triggers into your development workflow.
It's open source, so you can run a self-hosted version if your organization requires it. This makes it easy to switch if new compliance or security requirements forced you to house all source code on a private network.
Cons
Third-party integrations. Many developer tools integrate deeply with GitHub, but lack support for Gitlab. Gitlab does have webhook support so it's possible to build your own integrations, but this can be time-consuming.
Gitlab's main competitor (GitHub) has a massive social network of coders and hosts nearly all popular open source projects. If you are looking for this type of community, Gitlab may not be for you.
Customer support & reliability. In the time I've used Gitlab, it's not uncommon to experience hours-long periods of downtime without any announcement or indication from the support team when it will be available again.
Likelihood to Recommend
Gitlab is great for small companies looking for a cheap solution for hosting a large number of private repositories. It helps if you have experience with dev-ops tooling, as you may have to build some third-party integrations you would otherwise get out of the box with Github. It's also great if there is a possibility you would wish to migrate your repositories to a self-hosted network.
If you're an independent developer or organization whose main goal is to build a community around your open source projects, I would recommend choosing GitHub over Gitlab as the community is much larger and involved over at GitHub.
I use Gitlab in my company to keep all the projects updated in the cloud, any change or new ticket generated by the clients and developed in a test branch and then passed to quality so that it is tested and later deployed in production. I love this version manager because it provides an easy to use interface and quick to synchronize incidents and milestones in each project.
Pros
Wide community with a lot of documentation
Easy access to repository and with SSH security
Easy integration with groups of large and small jobs.
Cons
the free version sometimes gets a little slow and has 502 errors
little documentation for the Hispanic community.
ou can improve with more efficient and affordable plans.
Likelihood to Recommend
When we want to integrate different projects developed with work teams from different countries, it is perfect. It is not necessary to work physically in the office, with SSH security the code is traveling safely whenever and wherever you are.
We use GitLab to host our private applications that we build for clients. We also use GitLab to build and deploy our own website. We are a technology focused company writing applications, scripts and tools for ourselves and our customers. All of the code we write gets committed to GitLab repositories. GitLab CI makes it super simple for our code to go from commit to production. We deploy code to Kubernetes and GitLab CI gave us templates to craft our deployments with.
Pros
GitLab CI makes it dead simple to add continuous integration to any project.
GitLab's Docker container makes setting up your GitLab server easy.
GitLab provides a free way to host your own private repositories.
Cons
If you want to run GitLab yourself, you have to do all of the heavy lifting.
Navigation into projects can be difficult if you are part of a lot of groups.
Likelihood to Recommend
GitLab is very well suited if you need to host private repositories and don't have the budget to pay for services like GitHub. GitLab is not very well suited for large open source projects. It's not as ubiquitous as GitHub and thus the user base on GitLab.com is much smaller.
Gitlab was used by the entire engineering team (developers and operations) to hold all the code for all our projects. It was installed on-premise since we had 1000 projects to hold. All teams throughout the company used it on a daily basis to share code and discuss merge requests and issues.
Pros
Great interface for merge requests and issues.
Great community. It's easy to interact with and propose new stuff.
Cons
Used Gitlab community edition for years and it solved all my complaints during these years.
Likelihood to Recommend
In case you have many repositories and want some on-premise, Gitlab is the best thing you can get. For new startups looking for a great a great (or free) place to have private repositories, Gitlab is the best option you will find as well. It also has an integrated CI for your project, which is really nice.
We use gitlab for source code management of our integration test code. Gitlab has been crucial when working with remote users, offshore or nearshore, in ensuring code quality and stability of our builds. It also integrates with many of our existing tools to create a streamlined pipeline of work for our users providing feedback at every stage of the process.
Pros
branching
merge requests
integration with other tools
Cons
jira integration
Likelihood to Recommend
Gitlab is great in any environment where source code version is required. It is very similar to github.com with it's feature set but it also has a set of unique features such as build pipeline (we haven't used it yet). The features are constantly being added and they reflect industry's direction with features such as Docker integration.
Consolidates code to a trusted platform enabling Developers to collaborate on projects easily. Easy setup and integration with AD. The Gitlab platform is an essential part of your Continuous Integration platform.
Pros
Integration with software used to automate your deployments
GitLab UI is clean and simple
Run on their own webserver / database cluster
Cons
More robust DB
Include a function/plugin to check code for security/errors
Likelihood to Recommend
Gitlab is well suited for internal development. We have not tried to use Gitlab with external outside the company resources.
VU
Verified User
Director in Information Technology (1001-5000 employees)
