GitLab Ultimate
GitLabExternal reviews
873 reviews
from
and
External reviews are not included in the AWS star rating for the product.
GitLab: A Powerful and Wonderful DevOps Platform for Engineering Teams
What do you like best about the product?
GitLab is an exceptional all-in-one DevOps platform that offers a wide array of tools for the entire software development lifecycle — from planning to CI/CD to monitoring. It stands out due to its integrated approach, allowing teams to manage repositories, pipelines, issues, merge requests, and security all within a single interface.It is easy to collaborate, review, and enforce quality gates with approval rules, code owners, and discussions.
What do you dislike about the product?
The self-hosted version of Gitlab can be heavy on memory and CPU, requiring significant system resources.
What problems is the product solving and how is that benefiting you?
GitLab solves several key problems across the software development lifecycle, and here’s how it benefits me. GitLab CI/CD automates builds, testing, and deployments, reducing human error and speeding up time to production. GitLab encourages collaboration with built-in merge requests, inline code reviews, and issue boards, keeping all stakeholders aligned.
The best service for all your version control system
What do you like best about the product?
1. Clean UI
2. Quick responsive times for every action
3. All in one place for all your access tokens, repos, pipelines and much more
4. Best customer response
5. Easy navigation and compartmentalization
6. It's easily possible to integrate it with other tools like Slack, GitGuardian, etc
7. My goto tool to use it everyday as a senior engineer, be it code reviews or self review or managing pipelines
2. Quick responsive times for every action
3. All in one place for all your access tokens, repos, pipelines and much more
4. Best customer response
5. Easy navigation and compartmentalization
6. It's easily possible to integrate it with other tools like Slack, GitGuardian, etc
7. My goto tool to use it everyday as a senior engineer, be it code reviews or self review or managing pipelines
What do you dislike about the product?
I'd like to have a way to quickly connect to support or ask a question to a bot instead or reading through documentation
What problems is the product solving and how is that benefiting you?
CI/CD pipelines, integrations with Slack and GitGuardian, Version control and review of MRs + managing team members
Best tool to run production pipelines
What do you like best about the product?
Its an best tool to run pipelines very easily and also take less time to execute the commands in it.
What do you dislike about the product?
So far i dont see any drawback with gitlab in my project
What problems is the product solving and how is that benefiting you?
Mainly in my project we come across multiple failures due to bad duplicate data issue,gitlab helps u to remove those duplicate bad data by running pipelines in less time.
A Great DevOps Platform with Everything in One Place
What do you like best about the product?
What I like most is the GitLab brings together version control, CI/CD, issue tracking, and project management in a single tool. I really like how seamless it is to go from writing code to deploying it, all without leaving the platform. The built-in CI/CD is easy to set up, and the merge request workflow helps keep code quality high.
What do you dislike about the product?
It can feel a bit slow sometimes, especially with larger repositories or more complex pipelines. Also, some settings and permissions are buried deep in menus, so it takes a while to find things unless you use it regularly. The UI could use a bit more polish in places.
What problems is the product solving and how is that benefiting you?
GitLab helps my team keep all our DevOps work in one place, making collaboration between developers, testers, and operations much smoother. We no longer need to rely on separate tools for CI/CD, version control, and issue tracking—it’s all built into GitLab. This reduces context switching and makes onboarding new team members easier. The automation in pipelines also helps us catch issues earlier and deploy updates faster.
Development workflows improve with effective code reviews and user-friendly interface
What is our primary use case?
Our primary use case for GitLab involves software development, such as storing sources, automation, and pipelines.
What is most valuable?
The features I find most useful for our development workflows include Git, merges, branches, code reviews, and pipelines. The code review tool is pretty good, and its general usability is commendable when compared to GitHub. It is user-friendly, easy to use, and easy to administer. GitLab handles a significant amount of repositories, sources, and users effectively without data loss, even though it may slow down occasionally.
What needs improvement?
One significant feature we lack is the configuration that enforces code reviews, which simplifies the development life cycle. Unfortunately, this is available only at a higher license level than we currently use. Additionally, improvements are needed for stability, as the system tends to degrade over a few days and often requires a restart.
For how long have I used the solution?
I have been working with GitLab for approximately six years.
What do I think about the stability of the solution?
The self-hosted version of GitLab is not very stable when under load. It slows down and requires restarts every few days. The updates are frequent and demanding, happening at least once a week due to security reasons. While understandable, this often breaks running pipelines.
What do I think about the scalability of the solution?
In terms of scalability, GitLab in the cloud is easy to scale, but the self-hosted version is moderately easy, requiring some skills.
How are customer service and support?
We have contacted support in a couple of situations, and they were responsive and okay.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We have used Subversion, GitHub, and GitLab.
How was the initial setup?
The cloud-based setup is straightforward and easy. However, self-hosted setup is complex, requiring good DevOps and significant orchestration.
What's my experience with pricing, setup cost, and licensing?
The pricing and cost are on par with other tools and are neither too expensive nor cheap.
Which other solutions did I evaluate?
I have evaluated Subversion, GitHub, and GitLab.
What other advice do I have?
For those wanting to use GitLab, I recommend going with the cloud version as self-hosting is problematic. I rate GitLab an eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Improved agility and time to market with CI/CD enhancements
What is our primary use case?
We use GitLab for deploying our applications into different environments. It serves as more of a DevOps platform.
What is most valuable?
The CI/CD pipelines in GitLab are highly valuable. Another important feature is the single source of repository, allowing efficient repository management and source code management. GitLab provides manageability by allowing us to manage source code effectively through separate repositories. Additionally, GitLab enables the creation of individual CI/CD pipelines for each repository, making software more agile. By integrating GitLab as a DevOps platform, we have enhanced agility, improved our time to market, and different teams can work collaboratively on various projects.
What needs improvement?
GitLab should embed security features when dealing with source code. It is essential to conduct proper testing, such as unit tests and code coverage, within the SDLC pipelines. Incorporating tools like JMeter or load testing into the pipelines would be beneficial.
For how long have I used the solution?
I have been working with GitLab for around four to five years.
What was my experience with deployment of the solution?
The deployment process with GitLab takes approximately half an hour to forty-five minutes, which is not very time-consuming.
What do I think about the stability of the solution?
I have no complaints regarding stability. GitLab maintains an availability of 99% plus.
What do I think about the scalability of the solution?
Currently, GitLab is not easy to scale because GitLab has specific deployment instructions. We deploy it on one of the VMs. For scaling, other deployment options from GitLab's side need to be adopted. Vertical scaling is different from horizontal scaling, and there are different types of scalability.
How are customer service and support?
GitLab's support is very helpful. They utilize a severity and priority ticket system, with corresponding SLAs, to address our inquiries efficiently. The support team is quite knowledgeable.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
I previously used Jenkins. However, GitLab is a better tool because Jenkins requires different plugins which need to be installed and managed individually, whereas GitLab is a more complete DevOps platform, requiring minimal integration.
How was the initial setup?
GitLab is easy to set up, with guided instructions and documentation making the process straightforward. On a scale from one to ten, I would rate the ease of setup as eight.
What was our ROI?
Since adopting GitLab as a DevOps platform within the entire SDLC process, we have become more agile and improved our overall time to market.
What's my experience with pricing, setup cost, and licensing?
GitLab is somewhat expensive. The cost depends on the subscription plan adopted, such as premium or ultimate, typically charged per user.
Which other solutions did I evaluate?
Jenkins is another tool I evaluated before choosing GitLab.
What other advice do I have?
GitLab is a great tool that simplifies management and reliability. It allows the creation of individual CI/CD pipelines for different repositories, enhancing agility and helping software development teams expedite market delivery. I rate GitLab nine out of ten in overall satisfaction. My overall rating for GitLab is 9.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
A great repository and ticket tracking management tool all in one place
What do you like best about the product?
The repository can show issues in a Kanban style format making it easier to see tickets linked to MR requests and workflows
What do you dislike about the product?
Reporting. Unlike something like JIRA, the customisation options for reports are limited. I was trying to export a list of tickets where labels have changed from In QA to In Progress (gone back in the workflow) but the options weren't really there.
What problems is the product solving and how is that benefiting you?
There's many things. Mainly bug and ticket/feature tracking via Kanban and labels. We can see MR's linked to tickets and features allowing code or tests to be reviewed .
very useful and easy to use ci/cd pipeline tool
What do you like best about the product?
I like how easy it is to create pipelines with jobs and stages, use of variables and the concept of default runners and also ability to configure custom runners.
What do you dislike about the product?
The configuration of default runners is unknown - unless we run a particular command like uname
What problems is the product solving and how is that benefiting you?
Prior to using gitlab, i was building my code on a VM. when the VM went down or the network was down I was stuck. Also space was a constraint on VM with multple users using to store their files and build code.
moving to gitlab and having multiple projects eased this situation.
Also with the concept of branches I could have multiple flavors and options to achieve different functionality.
moving to gitlab and having multiple projects eased this situation.
Also with the concept of branches I could have multiple flavors and options to achieve different functionality.
Best CI/CD enabler
What do you like best about the product?
Gitlab is not just a code repository it can be used as a orchestrator and help with implementing dataops , gitops like architectures.
What do you dislike about the product?
Nothing as such , May be more powerful and cloud based runner availability.
What problems is the product solving and how is that benefiting you?
We have implemented dataops methodology using gitlab as a base and integrated all the tools around it
Streamlined collaboration with room for better project planning features
What is our primary use case?
The broad use of GitLab is for code check-ins, but I also use it for issue management and backlog management. It has integration with testing tools as well, and I utilize those features. GitLab supports code collaboration alongside issue and backlog management. Everyone within my team or pod, as we call it, can see each other's issues. The scrum master can look at the velocity and the burn-down charts.
What is most valuable?
I find all the CICD pipelines valuable, along with the simplicity it offers developers. When comparing it, certain features available in Jira are not present. Specifically, the ability to have weights at the milestone and epic levels does not exist. However, the security features are good and restrictive.
What needs improvement?
Certain features in Jira are not available in GitLab, such as the functionality to have weights at the milestone and epic levels. Hopefully, these features will be resolved with work items in GitLab. Also, if the child items are open in GitLab, closing the parent should not be allowed. While GitLab is a great tool for developers, it lacks project planner features. Roadmaps and Gantt charts in GitLab are not as advanced as in Jira, and changing start and end dates is more laborious in GitLab. Bridging the gap for project planners would make GitLab a more complete tool.
For how long have I used the solution?
I have been using it for about a year.
What do I think about the stability of the solution?
I have not really encountered stability issues. I would rate it probably an eight.
What do I think about the scalability of the solution?
I would say the solution is easy to scale.
How are customer service and support?
I do not have direct contact with customer service. We have relationship managers who deal with GitLab directly.
How would you rate customer service and support?
Neutral
How was the initial setup?
The initial setup was relatively easy.
Which other solutions did I evaluate?
In my company, the number of users is around ten thousand. If we are talking about my project, the figure is probably more around the three hundred mark, but it will grow to about six hundred users. In my company, that figure would be anything between five and ten thousand people.
What other advice do I have?
I would rate it an eight out of ten. Also, maybe, if GitLab is supporting any AI-driven projects or if it has any automation elements, it supports them. We have AI-driven projects where the code is stored in GitLab. GitLab Copilot is something we are looking to introduce soon. If you want to maintain your issues in GitLab and raise your book of work and features, then GitLab is a great tool for collaboration and integration with code deployment and CICD pipelines.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
showing 31 - 40