We have a normal use case to build source code and our agenda and then try to deploy it. The deployment is not specifically automated, it is semi-automated. So it is normal. We create an artifact, try to build it, and then deploy it onto the application server. It's not fully automated.
Provides or mandates quantitative code into the Master
Pros and Cons
- "We like that we can create branches and then the branches can be reviewed and you can mesh those branches back. You can independently work with your own branch, you don't need to really control the core of other people."
- "I would like to see static analysis also embedded in GitLab. That would also help us. If there's something that it does internally by GitLab and then that is already tied up with your pipeline and then it can tell you that you're coding is good or your code is not great. Based on that, it would pass or fail. That should be streamlined. I would think that would help to a greater extent, in terms of having one solution rather than depending on multiple vendors."
What is our primary use case?
What is most valuable?
At this point, I think the features are declining.
We like that we can create branches and then the branches can be reviewed and you can mesh those branches back. You can independently work with your own branch, you don't need to really control the core of other people.
There could be more features in GitLab, but we are as of now not using the full-fledged feature set.
Another good feature is the code review, which also helps us with peer review. It helps in giving part of the code and giving back whatever the branch that the developer is working on. It can then be merged once it is thoroughly reviewed. Those are certain things that I think are helpful from a developer's point of view. It provides or mandates quantitative code into the master.
What needs improvement?
We do reviews as I also work with some of the leadership teams. Leadership teams generally focus on statistics, metrics, or some sort of dashboard. They would like to have the ability to categorize these things. They would like to have a very high-level view. That would help. Someone who is not really a developer, but a leadership team. They are always interested in statistics or metrics features. That is something I would see imbedded into GitLab. That would help someone who is from the outside take a view and understand how qualitative the code is, because they cannot definitely dive in and look at the code, and they will not be able to understand all the details. At a high level, if they want to see and understand, at least they will have some confidence about how the projects are going on.
For how long have I used the solution?
I have been using GitLab for two years.
Buyer's Guide
GitLab
December 2024
Learn what your peers think about GitLab. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
823,875 professionals have used our research since 2012.
What do I think about the stability of the solution?
The stability is good. I never had any issues. Stability-wise, I'm comfortable with it.
What do I think about the scalability of the solution?
Scalability-wise it is very scalable as well. Based on the code volume, there is a scope for improvement. I never had issues with scalability.
How are customer service and support?
Technical support depends on licensing. We haven't reached out that frequently because it is stable and we don't see any issues. I don't recall anything that we had any particular challenge that we had to reach out immediately to GitLab and then get the answer quicker at any point in time.
How was the initial setup?
I wasn't here for the deployment but the deployment takes around 10 minutes.
Only a few aspects will take close to five minutes.
What other advice do I have?
I would rate GitLab an eight out of ten.
GitLab provides some sort of static analysis part. That is what I understand, but I never tried it. I would like to see static analysis also embedded in GitLab. That would also help us. If there's something that it does internally by GitLab and then that is already tied up with your pipeline and then it can tell you that you're coding is good or your code is not great. Based on that, it would pass or fail. That should be streamlined. I would think that would help to a greater extent, in terms of having one solution rather than depending on multiple vendors.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Has good pipeline features, but UI is not user-friendly
Pros and Cons
- "The solution's most valuable features are pipelines."
- "It has fewer options, and its UI is not so user-friendly."
What is most valuable?
The solution's most valuable features are pipelines. GitLab allows you to automate things and show them diagrammatically.
What needs improvement?
The solution is much harder to get around and organize extra features. It has fewer options, and its UI is not so user-friendly.
For how long have I used the solution?
I have been using GitLab for one year.
What do I think about the stability of the solution?
GitLab is a very stable solution.
I rate the solution’s stability an eight out of ten.
What do I think about the scalability of the solution?
I rate the solution’s scalability a seven out of ten.
How was the initial setup?
Although the solution's documentation is publicly available, you have to invest much more time to read everything and understand how to get around.
On a scale from one to ten, where one is very easy and ten is difficult, I rate the solution's initial setup a six to seven out of ten.
What's my experience with pricing, setup cost, and licensing?
The solution's pricing is acceptable.
On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a six out of ten.
What other advice do I have?
I got familiar with the CI part of the tool. If you want to use all the features for testing and packaging, you have to use the paid version.
Overall, I rate the solution a six out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Last updated: Jul 21, 2024
Flag as inappropriateBuyer's Guide
GitLab
December 2024
Learn what your peers think about GitLab. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
823,875 professionals have used our research since 2012.
IT Analyst at Envidia Graphics Private Limited
Useful code management, scales well, but lacking AI
Pros and Cons
- "The most valuable features of GitLab are the CI/CD pipeline and code management."
- "Merge conflicts and repository maintenance could improve. If there is someone new to the system they would not know if there is a conflict."
What is our primary use case?
We are using GitLab for team collaboration, code management, and certain CICD pipelines.
What is most valuable?
The most valuable features of GitLab are the CI/CD pipeline and code management.
What needs improvement?
Merge conflicts and repository maintenance could improve. If there is someone new to the system they would not know if there is a conflict.
In a feature release, it would be helpful if there was AI integrated into the system. For example, if there was a CI/CD pipeline available, we could configure them for our purpose without doing the process manually.
For how long have I used the solution?
I have been using GitLab for approximately four years.
What do I think about the stability of the solution?
I rate the stability of GitLab a seven out of ten.
What do I think about the scalability of the solution?
I rate the scalability setup of GitLab a seven out of ten.
Which solution did I use previously and why did I switch?
I have experience using GitHub, but GitLab is a superior platform. One major advantage of GitLab is the ability to maintain a private cloud with a wide range of features. It also allows for quick setup of CI/CD pipelines. Garrett is becoming popular amongst developers for code maintenance.
How was the initial setup?
The initial setup of GitLab takes a long time because there is a lot to configure.
I rate the initial setup of GitLab a seven out of ten.
What other advice do I have?
I rate GitLab a seven out of ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer:
Tool Manager at a computer software company with 10,001+ employees
Good for CI/CD and version control, highly scalable, and very easy to set up
Pros and Cons
- "CI/CD is very good. The version control system is also good. These are the two features that we use."
- "I would like more Agile features in the Premium version. The Premium version should have all Agile features that exist in the Ultimate version. IBM AOM has a complete Agile implementation, but in GitLab, you only have these features if you buy the Ultimate version. It would be good if we can use these in the Premium version."
What is our primary use case?
We use it for version control and CI/CD.
What is most valuable?
CI/CD is very good. The version control system is also good. These are the two features that we use.
What needs improvement?
Its security features are very expensive. The Ultimate version is very expensive.
I would like more Agile features in the Premium version. The Premium version should have all Agile features that exist in the Ultimate version. IBM AOM has a complete Agile implementation, but in GitLab, you only have these features if you buy the Ultimate version. It would be good if we can use these in the Premium version.
For how long have I used the solution?
I have been using GitLab for five years.
What do I think about the stability of the solution?
It is very stable. In five years, we had to fix it only once.
What do I think about the scalability of the solution?
It is very scalable. We have about 2,000 users, but as per the reference architecture documentation, it can be scaled up to 50,000 users.
How are customer service and support?
We are using the open-source free version. So, we don't have support. We are looking to buy the intermediate version or Premium version.
How was the initial setup?
It was very easy to set up.
What about the implementation team?
We set it up by ourselves. We also update it, and we don't have to turn it off.
What's my experience with pricing, setup cost, and licensing?
We are using its free version, and we are evaluating its Premium version. Its Ultimate version is very expensive.
Which other solutions did I evaluate?
We are evaluating its Premium version, and we are also evaluating other products like GitHub.
What other advice do I have?
I would rate it a nine out of 10.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
CTO at Dokument IT d.o.o.
With great integration capabilities for small companies, the tool also provides a reasonable amount of stability
Pros and Cons
- "The solution's most valuable feature is that it is compatible with GitHub. The product's integration capabilities are sufficient for our small company of 35 people."
- "We do face issues in our company when we run out of disk space."
What is our primary use case?
My company's programmers use GitLab for everyday development purposes.
What is most valuable?
The solution's most valuable feature is that it is compatible with GitHub. The product's integration capabilities are sufficient for our small company of 35 people.
What needs improvement?
Some of the programmers in my company have had complaints about the product.
We do face issues in our company when we run out of disk space. We had to do some low-level system interventions to recover the server from GitLab in our company. It would be good if GitLab implemented some diagnostic features so that the server prevents functioning when it detects insufficient disk space. It is important to prevent cache to avoid running out of disk space. Considering the aforementioned details, making a recovery wasn’t simple.
For how long have I used the solution?
I have experience with GitLab.
What do I think about the stability of the solution?
Stability-wise, I rate the solution a nine out of ten.
What do I think about the scalability of the solution?
Owing to the small size of my company, we do not need to utilize the scalability feature of the product.
My company has around 20 users of the product.
How was the initial setup?
The initial setup of GitLab was okay.
The setup phase was completed in a day.
Our company has DevOps and CI/CD to help us with the deployment process of the product.
Though I am unsure, I feel that the solution is deployed on-premises.
What about the implementation team?
The deployment phase was carried out with the in-house members of our company.
What's my experience with pricing, setup cost, and licensing?
Speaking about the pricing of the solution, my company uses GitLab Community Edition.
Which other solutions did I evaluate?
Before choosing GitLab, my company had considered Microsoft TFS during the evaluation phase.
What other advice do I have?
GitLab is a product managed by the department of programmers in our company, and I am not much involved in it.
I recommend the solution to those planning to use it.
I rate the overall product a ten out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Researcher at the InfoCloud Research Group at a university with 1,001-5,000 employees
Efficiently streamlines and automates tasks
Pros and Cons
- "CI/CD and GitLab scanning are the most valuable features."
- "There is room for improvement in GitLab Agents."
What is our primary use case?
My primary use case is for creating pipelines and automation workflows.
How has it helped my organization?
By streamlining tasks that we used to do on a daily basis and scheduling them.
What is most valuable?
CI/CD, GitLab scanning, and the cloud are the most valuable features.
What needs improvement?
There is room for improvement in GitLab Agents.
I would like to see more features focused on GitLab or CICD. I am not sure if there is a roadmap for GitLab CI/CD Elite.
For how long have I used the solution?
I have been using GitLab for five years. I am currently using version 14.5.
What do I think about the stability of the solution?
It is a stable solution. I would rate it an eight out of ten.
What do I think about the scalability of the solution?
I would rate the scalability of GitLab a three out of ten. It is low.
It can be challenging to scale. Sharing databases and removing multiple VPNs is not easy to handle. GitLab's stability is not as good as other platforms that offer Kubernetes engines. We use OEMs instead.
There are 300 to 400 users in my company. We definitely plan to increase the usage.
Which solution did I use previously and why did I switch?
We are familiar with GitHub.
How was the initial setup?
I'll give the initial setup a six, slightly above average, where one is difficult and ten is easy.
Now we automate everything, so let's say the deployment now takes about one hour to deploy.
What about the implementation team?
For the deployment process, we create a template and prepare the VM on our cloud. Then we deploy the container using the controller, which deploys the solution.
We had IT specialists and engineers for the deployment process.
What's my experience with pricing, setup cost, and licensing?
It's a bit tricky because we have a different license. I rate the pricing mode a five out of ten for now, but it might change in the future. We have an educational license, and support is not included.
What other advice do I have?
GitLab offers various services, and it's important to understand which ones you truly need. Service providers might have different capabilities, and compatibility with your existing devices can be a critical issue. We haven't faced many problems with network compatibility or duplicated services so far.
If I could go back in time, I would recommend using GitLab primarily as a reliable repository. For additional features like scanning and monitoring, it might be beneficial to explore other specialized solutions.
Overall, I would rate the solution an eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Solution Engineer at a tech vendor with 10,001+ employees
A fantastic service delivery model with good security and stability
Pros and Cons
- "The solution's service delivery model is fantastic."
- "The solution should again offer an on-premises deployment option."
What is our primary use case?
Our company is a partner and installs the solution for clients who manage their ACD and DevOps pipelines.
We have 700 developers who use the solution, Microsoft's integration, and SharePoint for uploading.
What is most valuable?
The solution's service delivery model is fantastic.
Integrations connect to the cloud server and are easy to use.
The solution offers good security and stability.
What needs improvement?
The solution should again offer an on-premises deployment option. In the past, an on-premises solution was offered that used to sync with the cloud-based solution. We would like that option to return because many industries are interested in offline uploads and pathways.
The solution should integrate Web 3.0 and provide better system transactions.
For how long have I used the solution?
I have been using the solution for three years.
What do I think about the stability of the solution?
The solution is very stable.
How was the initial setup?
The initial setup is simple.
You can immediately start using the solution as soon as you subscribe.
What's my experience with pricing, setup cost, and licensing?
The solution is based on a subscription model and is reasonably priced.
Many options are available in the database but a few uncommon options that our company actually liked have been phased out. If those options return, the solution will be fantastic.
Our company subscribes to the premium tier which includes security. It would be nice to offer security as an add-on at lower tiers so more users have access to these advanced features.
I rate the cost an eight out of ten.
What other advice do I have?
I recommend the solution and rate it an eight out of ten.
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
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
DevOps Lead at Adidas
Great continuous integration and fast deployment
Pros and Cons
- "GitLab's best features are continuous integration and fast deployment."
- "GitLab's UI could be improved."
What is most valuable?
GitLab's best features are continuous integration and fast deployment.
What needs improvement?
GitLab's UI could be improved. In the next version, the documentation of the migrations steps should be better.
For how long have I used the solution?
I've been working with GitLab for six years.
What do I think about the stability of the solution?
GitLab is very stable.
What do I think about the scalability of the solution?
GitLab is scalable.
How are customer service and support?
GitLab's technical support is quick and responsive.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup is pretty simple for GitLab as a service, but it's more complex for a hosted solution.
What's my experience with pricing, setup cost, and licensing?
GitLab is comparatively expensive, but it provides value because it's feature-rich. I would rate its pricing four out of five.
What other advice do I have?
I would rate GitLab nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free GitLab Report and get advice and tips from experienced pros
sharing their opinions.
Updated: December 2024
Product Categories
Application Security Tools Build Automation Release Automation Static Application Security Testing (SAST) Rapid Application Development Software Software Composition Analysis (SCA) Enterprise Agile Planning Tools Fuzz Testing Tools DevSecOpsPopular Comparisons
SonarQube Server (formerly SonarQube)
Veracode
Snyk
Checkmarx One
Mend.io
Fortify on Demand
Sonatype Lifecycle
Acunetix
PortSwigger Burp Suite Professional
GitHub Advanced Security
HCL AppScan
Qualys Web Application Scanning
GitHub
Klocwork
Tenable.io Web Application Scanning
Buyer's Guide
Download our free GitLab Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- How does Microsoft Azure DevOps compare with GitLab?
- If you had to both encrypt and compress data during transmission, which would you do first and why?
- When evaluating Application Security, what aspect do you think is the most important to look for?
- What are the Top 5 cybersecurity trends in 2022?
- What are the threats associated with using ‘bogus’ cybersecurity tools?
- Which application security solutions include both vulnerability scans and quality checks?
- We're evaluating Tripwire, what else should we consider?
- Is SonarQube the best tool for static analysis?
- Why Do I Need Application Security Software?
- Which Email Security enterprise solution would you choose: Cisco Secure Email vs Forcepoint Email Security vs Barracuda Email Security Gateway?