Our primary use case is for source code maintenance, then doing the build and running code coverage tools like SonarQube, and then deployment.
GitLab Premium
GitLabExternal reviews
External reviews are not included in the AWS star rating for the product.
I am using GitLab in our company and it's great, nice CI/CD features.
Used for source code maintenance and provides user-friendly interface for code review and pull requests
What is our primary use case?
What is most valuable?
We have seen a couple of merge requests or pull requests raised in GitLab. I see the interface, the way it shows the difference between the two source codes, that it is easy for anyone to do the review and then accept the request; the pull request is the valuable feature.
What needs improvement?
We have only seen a couple of times on Gitlab, which we use for building some of the applications. Recently, we have heard that some of the builds were taking a long time or were not scheduled. In such cases, they had to contact the GitLab community or the GitLab organization to address these issues.
So, there is room for improvement in regard to the issues with build times.
In future releases, additional features could be added in post-deployment monitoring. Currently, GitLab supports CI/CD up to deployment. Anything that would assist in monitoring deployments, especially in the context of Kubernetes or Docker, would be valuable. It may not be necessary for enterprise-level use, but for midrange organizations, integrating post-deployment monitoring of infrastructures and generating reports could be beneficial.
For how long have I used the solution?
We have been using this solution for three years now.
What do I think about the stability of the solution?
The solution offers good stability. However, sometimes we do see some issues due to upgrades and patches. But a couple of times, we have seen build issues where it takes a long time, or it gets stuck, and people have to manually restart those.
What do I think about the scalability of the solution?
It is a scalable solution in our environment. We have over a thousand end users.
How are customer service and support?
The support is very good.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Earlier, we were using Atlassian products, and then we shifted to GitLab.
What about the implementation team?
The deployment is handled by a different team. For maintenance, we get good support from GitLab. For any production issues, we hear that we get good support from GitLab. That is something good.
What other advice do I have?
My advice would be it's a very good tool for developers, especially those spread across the globe. It has a very good interface for any pull request or code review. The CI/CD pipeline is also easily built in, so we can easily build and deploy it into various environments. So that eases the developer's and the production ops team's life.
Overall, I would rate the solution a ten out of ten.
Gitlab review
GitLab Flavored
Great DevOps platform support
With great integration capabilities for small companies, the tool also provides a reasonable amount of stability
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.
Best development platform and easy to use
Using GitLab for professional projects
Complexity of the tools
Performance
Documentation Quality
Customization and Integration Complexity
Security Considerations
More than just a Github alternative.
* Modern UI, with customization options
* Built in CI/CD pipelines
* More affordable pricing than GitHub
* Gitlab plugins
* Lack of AI based tooling and support
* Gitlab feels to have lesser active development, implying that feature development is slower.
* CI/CD: Setup autmoation to run tests on every push to main branch and then trigger a fresh build and deployment.
* Code review: We directly review each others code in commits via comments