GitLab: Best tool in class
September 27, 2024
GitLab: Best tool in class

Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with GitLab
We use GitLab for everything code from source control to CI/CD. In our area of business, we develop complete software solutions for both mobile and web, both frontend and backend.
GitLab is the best user experience for our teams of developer and we can see how much the tool is appreciated when comparing it to competitor products.
GitLab is the best user experience for our teams of developer and we can see how much the tool is appreciated when comparing it to competitor products.
Pros
- User experience: it's efficient to do my job
- Good visualization of everything in my git repository and good overview of my code history
- Good CI\CD functionality
Cons
- Better integration with diagramming tools like PUML: load a diagram from a PUML file
- Better Jira integration... not that we like Jira but for those that are forced to use it
- It is a critical tool for any development team that just wants to hit the ground running. CI\CD efforts are at least 50% using GitLab vs competitor products. Also maintaining them is better as usually a GitLab pipeline is 2/3s of the size (in lines) in comparison with what we can achieve with competitor products.
- You can combine task management and sourcecontrol into one tool.
- It helps doing complex merges or when things go wrong by offering us an overview of everything we need to know about code over time.
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution.
GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" in GitLab while you have to do clickops in GitHub to achieve the same.
No overview of code in branches is a minus when we tried to figure out what our colleagues are trying to merge as it looked off.
GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" in GitLab while you have to do clickops in GitHub to achieve the same.
No overview of code in branches is a minus when we tried to figure out what our colleagues are trying to merge as it looked off.
We are using a paid plan but no, we have not used any of the security features as we have our own solutions we are using.
Yes, we heavily used the CD part of GitLab for creating and testing builds.
It is way easier to use the GitLab CD functionality than other competitor products because their API is way easier to use, and the errors from GitLab were more intuitive, so it's faster to iterate setting pielines up.
Also, the pipeline code is small and logical, so it's easier to read and maintain.
It is way easier to use the GitLab CD functionality than other competitor products because their API is way easier to use, and the errors from GitLab were more intuitive, so it's faster to iterate setting pielines up.
Also, the pipeline code is small and logical, so it's easier to read and maintain.
Do you think GitLab delivers good value for the price?
Yes
Are you happy with GitLab's feature set?
Yes
Did GitLab live up to sales and marketing promises?
Yes
Did implementation of GitLab go as expected?
Yes
Would you buy GitLab again?
Yes

Comments
Please log in to join the conversation