We use CI/CD for producing a Docker image. Afterward, we use Argo CD with Helm for deployment on OpenShift. Initially, we had the open-source version, however, we upgraded to the Ultimate version for security scanning and other features.
GitLab Ultimate
GitLabExternal reviews
873 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Deployment time is reduced significantly with improved security features
What is our primary use case?
What is most valuable?
The CI/CD pipeline with Helm has significantly improved deployment speed and efficiency. Before using this solution, our deployments took four to five hours. Now, we can deploy applications in ten minutes. The Ultimate version offers enhanced features for security scanning through DAST and SAST analysis, which have greatly benefitted our project workflow.
What needs improvement?
The licensing model could be improved to be more accommodating in terms of user numbers and costs. This would serve more users better.
For how long have I used the solution?
I have been working with GitLab for three years.
How are customer service and support?
We use a partner, and they are very competent. We have not had the need to open a support ticket directly with GitLab.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
Before GitLab, we used Jenkins. We used GitLab as a Git repository and Jenkins for pipelines. With Jenkins, we produce Docker images and conduct tests and compile Java projects.
What was our ROI?
We have saved time significantly, reducing deployment time from four hours to five minutes per deployment.
What's my experience with pricing, setup cost, and licensing?
The price is high, and it limits user accessibility. When we shifted from the open-source to the Ultimate version, we had to reduce the number of users due to the licensing model.
Which other solutions did I evaluate?
We did not evaluate other options as we are currently satisfied with GitLab.
What other advice do I have?
I recommend GitLab for security features and rate it eight out of ten.
However, the licensing model could be more flexible to accommodate a broader user base. I especially recommend it for public companies and government-related entities.
Gitlab Experience was really good
What do you like best about the product?
CI/CD implementation with gitlab runners is really good.
Different types of runners is such a feasible option to integrate.
Different types of runners is such a feasible option to integrate.
What do you dislike about the product?
Sometimes the gitlab runners is not able to schedule a job for longer durations and it's quiet frustrating.
What problems is the product solving and how is that benefiting you?
It solves our CI/CD infrastructure by not relying on platform runners and we can do it complete in-house.
Very helpful for code sharing with team
What do you like best about the product?
Cherry pick feature for hotfix production release
What do you dislike about the product?
Sometime stash changes overidrd or conflict
What problems is the product solving and how is that benefiting you?
Code secure with we can create tag after every release and code share with team
Streamline building and deployment processes with user-friendly integration
What is our primary use case?
I am using GitLab primarily as a code repository and for CI/CD tools and deployments.
What is most valuable?
The feature I appreciate the most about GitLab is its ease of use and compatibility, which allows for straightforward building and deployment processes.
Continuous integration with deployment is very powerful, which is a significant reason for migrating from TFS to GitLab. Its documentation is extensive, and YAML files are user-friendly, making the deployment process more or less straightforward.
What needs improvement?
There are missing search features, particularly when searching repositories or applying filters. Additionally, I have encountered issues with the deployment of CI/CD pipelines, especially dealing with variable environments.
Creating a YAML file with numerous variables can be challenging without a way to separate them by different environments. It would be beneficial to have a user-friendly interface for setting up these configurations, instead of just writing YAML files.
For how long have I used the solution?
I have been working with GitLab for a little over a year as I transition from TFS.
What do I think about the stability of the solution?
The stability of GitLab is impressive. Everything, including runners, functions smoothly without any issues.
How are customer service and support?
Technical support from GitLab has been satisfactory. I have had meetings where they taught me, explained things, and provided guidance for starting from scratch. Overall, my experience has been pretty good.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
I am transitioning from TFS to GitLab, mainly due to the powerful continuous integration capabilities of GitLab.
What about the implementation team?
Currently, I have two developers partially dedicated to creating the CI/CDs, Firebend, and repositories.
What was our ROI?
Migrating to GitLab is bringing time-saving benefits, and everything is easier to automate. This transition is crucial for us.
What's my experience with pricing, setup cost, and licensing?
The pricing of GitLab is reasonable, aligning with what I consider to be average compared to competitors.
Which other solutions did I evaluate?
I am migrating from TFS to GitLab.
What other advice do I have?
I would appreciate some AI-driven helpers, similar to Visual Studio's Copilot, integrated into GitLab. This could enhance the user experience by providing assistance during configuration. I rate GitLab a nine out of ten points.
Optimize coding processes with efficient CI/CD while exploring AI integration
What is our primary use case?
We are using GitLab for source code configuration and for CI/CD processes.
What is most valuable?
The CI/CD process is very efficient. We are utilizing the pipelines extensively and gaining significant benefits from GitLab.
What needs improvement?
We are not using the AI process yet, however, I would like to see AI support in GitLab. Maybe it already does. I am not sure how it supports AI processes.
For how long have I used the solution?
We have been using GitLab for two years.
What do I think about the stability of the solution?
GitLab supports us very well.
How are customer service and support?
We do not have any direct technical support from GitLab. We ask questions to our IT department, and they may seek external support if needed.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We have just tried Jenkins. We are using GitLab. GitLab has better support, and its features are superior compared to Jenkins.
What about the implementation team?
The initial setup was handled by our IT department.
What was our ROI?
GitLab is a cost-saving tool and is particularly effective for coding processes.
What other advice do I have?
I do not have any recommendations or suggestions. I rate GitLab a ten out of ten.
Which deployment model are you using for this solution?
On-premises
Seamless integration and automation accelerate time to market
What is our primary use case?
What is most valuable?
GitLab's source control is excellent. Having the source control and pipeline in the same platform makes integration seamless. It is already integrated, with no need to configure any webhooks or other settings.
Implementing CI/CD with GitLab has accelerated the time to market significantly. As we implement automated testing and DevSecOps, it speeds up the process by forty to sixty percent.
What needs improvement?
GitLab should enhance its GitOps capability as they are currently using FluxCD, however, Argo CD is better and offers more features. GitLab should work on improving their user interface for GitOps as it is lagging behind.
For how long have I used the solution?
I have been working with GitLab for more than three years now.
What do I think about the stability of the solution?
GitLab is very stable with no issues in performance or availability.
What do I think about the scalability of the solution?
GitLab is highly scalable, but in our current architecture using Docker containers, it isn't. That is why we're transitioning to OpenShift for future scalability with increased user numbers.
How are customer service and support?
I have interacted with architects for some advice during the implementation, and they were prompt in their response. However, I have not had to open any support tickets yet.
Which solution did I use previously and why did I switch?
I have worked with several CI/CD tools, including Jenkins, Azure DevOps, Tekton, and Jenkins. GitLab CI is more powerful than Jenkins and Azure DevOps and comparable to Tekton.
How was the initial setup?
The initial setup of GitLab was straightforward. We have it installed as a Linux package and as a Docker container, which took very little time.
Which other solutions did I evaluate?
I have used Tekton before, the vanilla version on Kubernetes and Red Hat's version of the pipeline.
What other advice do I have?
Overall, I recommend GitLab to other DevOps teams due to its powerful CI capabilities and having most tools you need on the same platform. It enables seamless integration and automation. I rate GitLab nine out of ten.
Version management software for developers
What do you like best about the product?
1. It is a very useful software for code management.
2. We can manage our code of project into gitlab. We can manage our code by creating branch like master, staging, develop, feature and etc.
3. It is a version control software.
4. It is a open source software and easy to implementation. It can be used for DevOps.
5. We can do any integration into gitlab like CI/CD.
6. Many companies are mostly used this software for managing their code and documents as well.
7. This platform is very secure for security and we can track our project.
2. We can manage our code of project into gitlab. We can manage our code by creating branch like master, staging, develop, feature and etc.
3. It is a version control software.
4. It is a open source software and easy to implementation. It can be used for DevOps.
5. We can do any integration into gitlab like CI/CD.
6. Many companies are mostly used this software for managing their code and documents as well.
7. This platform is very secure for security and we can track our project.
What do you dislike about the product?
1. Sometime we were facing problem like intergration error.
2. There are some command facing issue like merge conflict.
3. We need some public repository on gitlab but unfortunatly it is not present in gitlab.
2. There are some command facing issue like merge conflict.
3. We need some public repository on gitlab but unfortunatly it is not present in gitlab.
What problems is the product solving and how is that benefiting you?
Before using GitLab, we had to manage our code directly on the server. However, this sometimes led to code being accidentally deleted, making recovery very difficult.
With GitLab, we can easily access all our code by using branches and previous commits. This is because GitLab is a version control tool, which is not only reliable but also user-friendly for DevOps teams.
With GitLab, we can easily access all our code by using branches and previous commits. This is because GitLab is a version control tool, which is not only reliable but also user-friendly for DevOps teams.
DevOps Platform With A Wide Range Of Useful Tools.
What do you like best about the product?
There are so many things which i like best about gitlb. It offers tools for software development as well as version control. It's continuous integration and continous deployment is of top notch. Very helpful for managing projects .
What do you dislike about the product?
For beginners it's UI feels complex and cluttered. And it's premium features are costly.
What problems is the product solving and how is that benefiting you?
Gitlab solves a major problem i.e time consumption. Because being a platorm having multiple functionality, an individual doesn't have to use seperate tools for CI/CD, version control and project management . For myself it will be easier for me to track progress and manage task efficiently.
Boosted productivity with automated pipelines and seamless collaboration
What is our primary use case?
I use GitLab to manage our development lifecycle. We use it to store code and automate our CI/CD pipeline. Once developers commit their code, the CI/CD pipeline automatically starts, supporting development through various stages. It is part of our software development life cycle.
What is most valuable?
GitLab enhances productivity and reduces time since many tasks are automated. I appreciate the team collaboration it offers, enabling multiple people to work on the same Git repository seamlessly.
Additionally, it streamlines our DevOps processes with automated CI/CD pipelines.
What needs improvement?
There are some challenges with repository file management as GitLab may struggle to manage larger files. Improvements could be made regarding size management and file partitioning.
Also, the UI has remained the same for a couple of years and could benefit from an update with AI features and better customization.
For how long have I used the solution?
I have been using GitLab for three or four years.
What do I think about the stability of the solution?
I have not encountered any performance or stability issues with GitLab so far. It has remained stable and reliable.
What do I think about the scalability of the solution?
GitLab is scalable as multiple users can simultaneously access it without issues.
How are customer service and support?
We have rarely needed to escalate issues to technical support since GitLab usually runs seamlessly. Occasionally, issues might arise if the URL isn't up or due to server problems.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I have worked with Bitbucket. In comparison, GitLab is more advanced, particularly in terms of cloud capabilities.
How was the initial setup?
Setting up GitLab is smooth and straightforward. There is no complexity as long as you're familiar with the basics. A simple code can be reused, facilitating easy installation and use.
What's my experience with pricing, setup cost, and licensing?
GitLab is mostly free, with potential costs arising from upgrade versions. There is a trial period of about six months during which it is free. Afterward, fees apply.
Which other solutions did I evaluate?
I have experience with Bitbucket and Jenkins, and both serve as alternatives to GitLab for version control and CI/CD pipelines.
What other advice do I have?
I recommend GitLab for DevOps engineers. It is easy and fast to use. While Jenkins is also good for understanding, GitLab offers an easier user experience. I rate GitLab as ten on a scale of one to ten.
Which deployment model are you using for this solution?
On-premises
Time saving for the better deployment
What do you like best about the product?
We not need to install any addition Pipeline softwear like jenkins , ansible the git lab will take care of pipeline and deployment with it yaml file
What do you dislike about the product?
The computer minutes
it will take the small linux machine to deploy where the compute minutes will consume more
it will take the small linux machine to deploy where the compute minutes will consume more
What problems is the product solving and how is that benefiting you?
with gitlab you can build the pipeline by default even though it has some compute minutes limitation, but it was useful for the freshers and startup business
showing 41 - 50