I am using GitLab primarily as a code repository and for CI/CD tools and deployments.
GitLab Premium
GitLabExternal reviews
External reviews are not included in the AWS star rating for the product.
Streamline building and deployment processes with user-friendly integration
What is our primary use case?
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?
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.
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.
How would you rate customer service and support?
Positive
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
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. 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.
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.
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?
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?
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.
Time saving for the better deployment
it will take the small linux machine to deploy where the compute minutes will consume more
Streamlines code management with efficient branch handling but needs improved conflict resolution
What is our primary use case?
We were using GitLab as a repository for our project. Whenever we were developing anything, we would commit our codes there.
We used it for creating branches, merging branches, and comparing branches to resolve conflicts during code committing. We configured the CI/CD pipeline to automate our deployment process. We also utilized it in conjunction with tools like Octopus and OpenShift.
How has it helped my organization?
GitLab helped us streamline our code-committing and versioning process. It provided better user-friendly solutions for comparing and resolving conflicts when committing code.
The CI/CD pipeline setup was straightforward and required fewer commands, making it simpler to use compared to Tekton. This efficiency in code management and deployment contributed to smoother operations in our projects.
What is most valuable?
The most valuable aspects of GitLab are the ability to create branches, merge branches, and compare branches to resolve code conflicts.
The documentation provided by GitLab is very comprehensive, which is useful for resolving queries. GitLab's logs are also beneficial for tracking the status of our CI/CD pipeline.
What needs improvement?
GitLab can improve its user interface to make conflict resolution more user-friendly. Better and more descriptive logs during CI/CD pipeline configuration would also be beneficial to diagnose issues more quickly.
Sometimes, the logs provided are not sufficient to understand the errors, and we needed assistance from our DevOps team.
For how long have I used the solution?
I have been using GitLab for around four to five years.
What do I think about the stability of the solution?
I have not experienced any performance or stability issues with GitLab so far.
What do I think about the scalability of the solution?
GitLab is scalable and works well with multiple environments. It integrates well with other tools. It has all the features required for our coding and deployment needs, which makes it scalable to our changing requirements.
How are customer service and support?
I did not have the opportunity to engage with GitLab's technical support as I did not encounter any issues requiring escalation.
How would you rate customer service and support?
Neutral
How was the initial setup?
The initial setup was straightforward. There were no challenges beyond typical configuration, and the documentation was adequate.
What about the implementation team?
Our DevOps team handled most of the configuration work, and we, as developers, made changes only occasionally for personal use scenarios.
What's my experience with pricing, setup cost, and licensing?
I have never paid for using GitLab personally, as it is free for our usage purposes. Even when working in other small organizations, we opted for GitLab as it was cost-efficient.
What other advice do I have?
I would recommend GitLab to others because it is free and user-friendly. It provides all the necessary functionalities we need.
I'd rate the solution seven out of ten.
Robust software development tool with excellent new features and good support
What is our primary use case?
What is most valuable?
GitLab is robust software and easy to use. There is excellent documentation available on their site but it can be overwhelming for early learners.
They incorporate new features every September, and they have introduced their own code editor and AI features.
What needs improvement?
The pricing has been substantially increased, which is a major concern. While GitLab has a lot of documentation, the complexity and volume can be overwhelming, especially for new learners. Structuring the documentation more effectively could help alleviate this issue.
For how long have I used the solution?
GitLab was resold for approximately two years.
What do I think about the stability of the solution?
The solution is stable, and there have been no noted glitches or latency issues.
What do I think about the scalability of the solution?
The solution is easy to scale.
How are customer service and support?
Customer service and support are good.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Previously we worked as resellers of other IT software like Snyk and Aqua Cloud Security.
How was the initial setup?
The initial setup is medium in terms of difficulty. It's neither too easy nor too difficult.
What's my experience with pricing, setup cost, and licensing?
Pricing is relatively expensive.
Which other solutions did I evaluate?
Previously explored solutions like Snyk and Aqua Cloud Security.
What other advice do I have?
GitLab is a very good solution.
I'd rate the solution nine out of ten.
Used for CI/CD, integration, and deployment
What is most valuable?
We use GitLab in the new project for CI/CD, integration, and deployment.
What needs improvement?
You need to have a good knowledge of the product in order to use it.
For how long have I used the solution?
I have been using GitLab for six months.
What do I think about the stability of the solution?
GitLab is a stable solution, and we haven’t faced any bugs.
What do I think about the scalability of the solution?
Around 40 people are using the solution in our organization.
Which solution did I use previously and why did I switch?
We previously used SVN and Jenkins. We switched to GitLab because it is an advanced tool with many new features.
How was the initial setup?
The solution's initial setup is easy if you follow the official document.
What's my experience with pricing, setup cost, and licensing?
We are using the free version of GitLab.
What other advice do I have?
I am working with the latest version of GitLab. I would recommend the solution to other users based on their requirements. It is easy to learn to use GitLab if you understand Git commands.
Overall, I rate the solution a nine out of ten.