As a DevOps Engineer for personal project gitlab is easy to use and has a smooth deployment process.
What do you like best about the product?
Automate the CI/CD pipelines. All in one-platform
What do you dislike about the product?
Limited features on free plan. UI is slow
What problems is the product solving and how is that benefiting you?
To automate the deployment to the cloud. Providing the smooth and easy to use experience. Also have a strong permission control.
My Gitlab Review
What do you like best about the product?
The best part is that the CI/CD feature comes directly integrated.
What do you dislike about the product?
The downside is that it consumes a lot of system resources when you install it on your own server.
What problems is the product solving and how is that benefiting you?
I add my software projects and use it to review my teammates' codes and for CI/CD processes.
Project management integration and development simplicity drive efficiency
What is our primary use case?
My most common use cases for GitLab are development and managing repositories, primarily focused on code development work.
What is most valuable?
The features that are really useful for my use case generally include pulling, merging, and ensuring the pipeline is upright, which are very intuitive.
It helped me personally and my team to save time and money.
In terms of impact from using GitLab as an all-in-one DevOps platform, it helped with my project development life cycle.
What needs improvement?
Regarding improvements, making task management is something that GitLab can potentially make easier, similar to what DevOps or Jira does.
For how long have I used the solution?
I have been working with GitLab for about two years.
What was my experience with deployment of the solution?
The deployment and initial setup were not difficult for me to complete. The pipeline management was easy.
The setup process took less than an hour.
What do I think about the stability of the solution?
In terms of project management overall, I haven't faced any issues such as downtimes or losing the repository.
How are customer service and support?
I haven't contacted technical support of GitLab.
How would you rate customer service and support?
Which other solutions did I evaluate?
When comparing GitLab with GitHub, I haven't really seen any noticeable difference.
What other advice do I have?
I have worked with Azure DevOps before and found it really intuitive to use.
I have used GitHub and GitLab as well, and I find that they've been fairly intuitive to use.
Regarding GitLab, I purchased an enterprise license, though I'm not aware whether I or my company bought this license from AWS Marketplace or elsewhere.
I'm not aware of any integration with other tools or third-party applications.
I haven't faced any difficulties with user interface or deployment.
On a scale of 1-10, I rate GitLab an 8.
I have a great experience in GitLab Friendly Use
What do you like best about the product?
I find GitLab CI/CD pipelines very intuitive and powerful. Setting up automated tests, deployments, or even custom jobs feels seamless.
What do you dislike about the product?
Compared to GitHub, community and third-party integration support can sometimes feel somewhat limited. That said, once you're familiar with it, the benefits often outweigh the initial learning curve.
What problems is the product solving and how is that benefiting you?
GitLab solves the problem of tool fragmentation by providing an all-in-one DevOps platform. Instead of using separate tools for version control, CI/CD, code review, issue tracking, and security scans, GitLab brings everything into one unified interface
Comprehensive DevOps Platform with Great CI/CD
What do you like best about the product?
Its built-in CI/CD pipelines are powerful and easy to configure, enabling seamless automation from code to deployment.
What do you dislike about the product?
The UI can feel cluttered at times, and some advanced features require a steep learning curve.
What problems is the product solving and how is that benefiting you?
GitLab consolidates the entire DevOps lifecycle into a single platform, reducing the need for multiple tools. This improves team collaboration, streamlines CI/CD processes, and accelerates delivery while maintaining code quality and security.
A Tool which rules CI/CD
What do you like best about the product?
I like best about gitlab is version control and ci/cd development and reduce context switching.I also like the role -based controls which make team collabration secure and effective.Its best to integration with other platfroms like data bricks.Also experienced personally the quick response of customer support
What do you dislike about the product?
Gitlab indeed has clean UI but its complexity to establish for new users is overwhelming.Some settings and features are deep layered inside settings and difficult to find and use .
What problems is the product solving and how is that benefiting you?
This platform solves problems related to collective working, versions, and continuous integration.The benefit I experienced is minimum complexity in managing and development of workflows.
Best tool for Planning and tracking your development and Deployement
What do you like best about the product?
Setting up our groups and Projects in best manner
Managing my backlogs and features
Managing story and its pipeline and tracking till deployment
Better tracking of Sprint and story movement from grooming to deployment.
Tracking teams logs and hours burned via dashboards for better visibliity
What do you dislike about the product?
Sometime commands fails and conflict resolution process is uneasy as TFS
What problems is the product solving and how is that benefiting you?
our daytoday development problems
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?
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.
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?
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?
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?
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.