Effortless Collaboration with Robust Automation
What do you like best about the product?
I like the automation feature in GitLab, which runs tests on its own every day. It's really helpful that it makes accessibility for other team members very easy, allowing us to actively collaborate on the project and maintain a common repository to be shared with everyone. Also, the initial setup of GitLab is very easy and straightforward.
What do you dislike about the product?
There's nothing specific like that. But the push and pull can be a bit better. The code, which I have pushed, if I can't revert a specific part of it, I have to revert everything back if there is any issue with the code.
What problems is the product solving and how is that benefiting you?
I use GitLab to store all project files and repositories in one place. It automates daily tests, enhancing accessibility and collaboration for my team.
All-in-One Platform for Code Hosting, CI/CD, and Issue Tracking
What do you like best about the product?
Good to store code and keep track of different issues include features:
Git repository hosting, CI/CD pipelines, Issue tracking & boards, Code reviews & merge requests, Container registry, Security scanning tools
What do you dislike about the product?
well most features are good and useful but UI is sometime slow if project is large, for self hosted it uses more resources. need to learn before uses else can get lost
What problems is the product solving and how is that benefiting you?
it helps keeping source code secure and within boundary of company for employee and client. keep list of tasks, bugs for project.
Integrated task tracking and documentation have streamlined collaboration and code workflows
What is our primary use case?
My main use case for GitLab is utilizing it in three main ways: one is using the Issues and Epics tracking for tasks, the second way is using the Wiki, which is the documentation feature, and then the third way is for code management.
Out of those three, I find myself using the Issues and Epics tracking feature the most often. I really quite like it because I find it clear and clean to use, and it works well when using it with numerous people.
We use the Issues feature to record our tasks and assign those out, as well as recording the description of what the task requires. Then we use the Epics feature to group the issues into categories, which makes it easier to track the tasks at a higher level.
What is most valuable?
In my opinion, the best features GitLab offers are the Issues and Epics feature, which I find very clean and clear to use, and it is very quick and responsive. I also quite value the Wiki feature because both of those are built into the same platform, making it very easy to bounce between the two and create links between the boards and the Wiki.
The ability to link between the boards and the Wiki helps my workflow and collaboration with my team by ensuring that if we have any tasks that need to be carried out, we have them on the Issues board, and we write runbooks in the Wiki on how to carry out the task. We copy the link of the Wiki and put it into the description of the tickets so that when someone is working on the ticket, they can very quickly go over to the Wiki and know how to carry out their task, which saves us time.
GitLab has positively impacted our organization by making our code very secure because GitLab prides itself on security. Storing code in GitLab is a very secure way to do it, and from an operational efficiency and time-saving perspective, the Issues and Epics board is definitely helpful, offering a few benefits operationally.
What needs improvement?
The only feature I have used in GitLab that I thought could be improved is their code generation feature. When I previously used it, some of my questions were met with responses saying that it did not know the answer, and some responses were incorrect as well. I understand this is something new for them, so they are still developing it, but I do not feel that it is in a position where I would use it regularly just because it is not very reliable right now.
For how long have I used the solution?
I have been working in my current field between five to ten years.
What do I think about the stability of the solution?
GitLab is very stable. I have not seen any instability issues.
What do I think about the scalability of the solution?
GitLab is highly scalable and could very easily scale to thousands of code repos, which is necessary for any organizational size.
How are customer service and support?
The customer support for GitLab is very good, and I have no complaints because they have always been quite helpful. I would rate the customer support a ten out of ten because I have never had any issues with them before, and they are very knowledgeable.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Personally, I have previously used GitHub and Bitbucket as well. I find that GitLab has the cleanest and clearest UI out of all of them, and it has numerous features, such as the Issues and Epics tracking feature, as well as the Wiki feature, which sets it apart.
What was our ROI?
I have seen a return on investment. Any company that generates its own code and develops applications needs a code base, so it is more of a necessity rather than choosing something because it results in a measurable benefit. However, in terms of operational efficiency, a ten to twenty percent increase in speed could quite easily be seen from using the Issues and Epics tracking feature.
What's my experience with pricing, setup cost, and licensing?
Regarding pricing, setup cost, and licensing, to my understanding, GitLab offers competitive rates. There are a few big competitors within this space, such as GitHub and Bitbucket, so GitLab prices themselves competitively.
Which other solutions did I evaluate?
Before choosing GitLab, I did evaluate other options, and the main competitors I considered were GitHub and Bitbucket. They are great as well, and all three are brilliant, but GitLab, in my opinion, has the cleanest UI, which sets it apart.
What other advice do I have?
I would recommend others to use GitLab because it is a great tool and there are not any real major drawbacks, just a minor one related to the AI code generation. I have given this review an overall rating of nine out of ten.
All-in-one DevOps platform that keeps our team aligned and shipping faster
What do you like best about the product?
Everything in one place - code, CI/CD, issues, and deployments. The CI/CD pipeline is powerful and easy to configure. Code review and merge requests work well for our workflow. The built-in container registry and package registry are convenient. GitLab Pages is great for hosting docs. The self-hosted option gives us control when needed. Overall, it streamlines our DevOps workflow.
What do you dislike about the product?
The UI can be slow, especially with large repos or many pipelines. Some advanced features are only in higher tiers. The search could be better. The interface can feel cluttered. Documentation is extensive but sometimes hard to find. Runner management can be tricky at scale.
What problems is the product solving and how is that benefiting you?
Before GitLab, we used separate tools for version control, CI/CD, and project management. GitLab consolidates everything, reducing context switching and improving visibility. The CI/CD pipelines automate testing and deployment, catching issues earlier. This speeds up releases and reduces manual work. Having code, issues, and pipelines in one place makes collaboration easier.
A great enterprise repository solution
What do you like best about the product?
The user interface is excellent. It makes tasks like viewing and searching code, opening and reviewing merge requests, as well as creating tags and managing pipelines, all very straightforward and accessible.
What do you dislike about the product?
There are some useful features, but for instance, the ability to add two reviewers to a merge request is restricted by a paywall. This limitation is disappointing, especially for a self-hosted solution where you would expect more flexibility.
What problems is the product solving and how is that benefiting you?
We rely on GitLab to host our version control, with our entire monorepo managed there. All of our upgrades are handled through merge requests, which streamlines our workflow. Additionally, we have an extensive network of pipelines in place to ensure that our code consistently functions as intended.
Streamlined CI/CD with GitLab's Powerful Features
What do you like best about the product?
I like that with GitLab we have control over our data since we deployed our own server and linked it with our domain. It has been particularly useful for automating workflows like Continuous Integration and Continuous Deployment, especially into Kubernetes environments. I also appreciate the ability to store secrets safely with GitLab, which adds an extra layer of security to our processes. Moreover, integrating GitLab with SonarQube for checking vulnerabilities in source code has been beneficial. After the initial setup on our AWS EC2 machine, everything works smoothly, which I really appreciate.
What do you dislike about the product?
Nothing anything at the moment
What problems is the product solving and how is that benefiting you?
We use GitLab to keep our data secure and link it to our domain. It automates workflows with CI/CD for k8s environments and safely stores secrets.
Unified DevSecOps with Strong CI/CD Pipelines
What do you like best about the product?
I appreciate how GitLab brings the entire DevSecOps lifecycle into a single unified platform, reducing tools sprawl and making my workflow more efficient. GitLab's built-in CI/CD pipelines are one of its strongest features. They are easy to configure using .gitlab-ci.yml, provide powerful automation, and eliminate the need for separate CI tools, making environment deployment easy. The initial setup was moderately easy, and I found GitLab's documentation very helpful in making the installation straightforward.
What do you dislike about the product?
While GitLab is a powerful and unified DevSecOps platform, there are areas where usability and performance could be improved, specifically the user interface complexity and pipeline speed and resource consumption.
What problems is the product solving and how is that benefiting you?
I use GitLab to create tasks and issues for employees, get updates from assignees, and prioritize issues. It unifies my DevSecOps processes, reduces tool sprawl, and enhances efficiency with its strong built-in CI/CD pipelines, automation, and no need for separate CI tools.
Feature-Rich Platform with a Slick UI
What do you like best about the product?
It's an all-in-one solution for hosting both the sources and the resulting artifacts, good integration to other tools
What do you dislike about the product?
I'm missing a way to orchestrate reviews/merges across multiple repos
What problems is the product solving and how is that benefiting you?
collaborating over code review
Very Efficient and Structured Solution for the whole Workflow from Management to Deployment
What do you like best about the product?
It started out with a very minimalistic approach, but over time, they have consistently enhanced their features and addressed bugs with better support for customer satisfaction. The platform is now easier to use and less complicated. It also integrates with all the popular mailing, communication, collaboration, and alerting applications. We use it for all our work tracking and releasing. Very easy to implement and build upon.
What do you dislike about the product?
Still has less features compared to peers. But it has everything we really need.
What problems is the product solving and how is that benefiting you?
It can be integrated seamlessly with all the popular apps for coding, releasing, testing and alerting logs and all the management workflows too.
All in one platform for code and project management.
What do you like best about the product?
GitLab brings everything into one platform. I can manage code, track issues, create pipelines, and review merge requests without switching tools. The built-in CI-CD is a big advantage as it saves time and makes the whole process smoother.
What do you dislike about the product?
I believe it has a bit of a learning curve. The interface has a lot of features, so it takes time to get used to where everything is.
What problems is the product solving and how is that benefiting you?
Helps me keep code, issues, and pipelines all in one place. It makes it easier to review code with teammates, track bugs, and move features from start to finish without losing context. This saves time and makes teamwork more organized.
