GitLab Reviews

We primarily use this solution for end-to-end CI/CD solutioning and deployment as well as infrastructure, architect and environmental management. In addition, we plan to use it for version control and SaaS solutioning and have heard it is great.

The SaaS setup is impressive, and it has DAST solutioning. It also has dependency check and scanning mechanisms. If we were using other solutions, they would have to be configured, and we would have to set them us as a third party, but GitLab is straightforward. GitLab is a single solution that helps us do everything we need.

The documentation in GitLab could be improved a bit. For example, their RBAC is role-based access, which is fine but not very good. It could also be improved a lot.

We have been using this solution for almost seven years. We are currently using version 15.2.1. We are using GitLab Cloud, and it is a public setup.

It is a stable solution, and we have not experienced any challenges.

It is scalable, but we need to pay extra costs.

The technical support is good, but it is available with paid solutions only. So we have to rely on their documentation or wait for community updates for the free tier or vendor solution.

It is a cloud solution, so we didn't have to do much. We just needed to create an account, and the solution was ready. It is gitlab.com.

I rate this solution an eight out of ten because it is a good tool.

GitLab is used for pipeline development, automation, and deployment.

It is easy to manage.

GitLab integrates well with other platforms.

The automation is good.

While I don't have any specific complaints about GitLab, there are always things that could be better.

Better support, for example, could be provided. The technology could be made simpler to use, it should not be overly complex.

It should be used by a larger number of people. They should raise awareness.

I have been working with GitLab for three years.

GitLab has a good level of stability. I haven't had many problems.

GitLab is used by between 500 and 600 people.

Support is good.

I have used a variety of tools, including Ansible, Terraform, Bitbucket, and Bamboo.

I don't mind the price because I use the free version.

The licensing fee could be less expensive.

I would recommend this solution to anyone who is interested in using it.

GitLab is very good. I would rate GitLab a nine out of ten.

Our primary use case is for source management.

I have found the most valuable feature is security control. I also like the branching and cloning software.

I would like to have some features to support peer review. It would be nice if I can input some comments and share them with the teams. But I am not sure if it is already included in some paid versions.

I have been working with GitLab now for the past three or four years now.

The stability of the current solution I would rate as a nine on a scale of one to ten.

The scalability on a scale of one to ten is around an eight or nine. We currently have around one hundred individuals using this solution on a daily basis.

The initial setup was straightforward.

We are currently using the open-source version.

I would recommend using GitLab and rank it a seven out of ten.

We use GitLab as a source code repository, terraform modules repository, generic packages repository and for our CI/CD pipelines.

The most valuable features of GitLab are the merge request approvals, package repository, and that GitLab CI/CD pipelines plans are written in YAML.

GitLab could improve the package repository. It does not have support for Conan packages revisions.

Additionally, better support for deploying GitLab in Kubernetes is needed (i.e. more mature helm packages and updated documentation).

I have been using GitLab for approximately five years.

The stability of GitLab is good.

GitLab is scalable. We only needed to add more resources to the VM. Horizontally, we were not able to scale it because we couldn't deploy it in Kubernetes correctly.

We have approximately 300 people using the solution in my organization.

I have not used the support from GitLab.

I previously used Gerrit and I prefer GitLab. It is much better in the interface and integration, it is much more than only Git software, it is more of a complete package.

The initial setup of GitLab is not complex. However, it can be difficult to deploy GitLab on Kubernetes.

The deployment of GitLab was done in-house.

The solution's standard license is paid annually. They have changed the pricing tiers and removed the bronze tier, which was the perfect sweet spot.
There is a free version available.

I rate the price of GitLab a seven out of 10.

I would recommend the solution to others. For a self-hosted version, I advise others to deploy it using Docker/Docker-compose, it is the easiest way. The solution has no maintenance. 

I rate GitLab a nine out of ten.

We use GitLab for all of our Git sources and it is mapped to our integrated solution for the complete ICG platform.

The most valuable features of GitLab are ease of use and highly intuitive UI and performance.

GitLab can improve by integrating with more tools, such as servers with Docker.

I have been using GitLab for approximately 11 years.

GitLab is a stable solution. We've never faced any issues.

Our current setup is with one server but GitLab overall can scale.

We have approximately 300 people using the solution. Most of the people are in the developers' teams, management, and tech leads that all log into GitLab.

GitLab can be used for enterprise-sized companies.

I have not used the support from GitLab.

I have previously used GitHub as a developer. GitLab looks similar to GitHub and it's helping the developer use it better.

We update the GitLab version annually for maintenance.

GitLab is a free solution to use.

I rate GitLab a ten out of ten.

We are using it for building mobile applications and web applications. I am supporting the code in GitLab. It is only for giving access to my development team, and I just see what merge requests are coming.

I like GitLab from the CI/CD perspective. It is much easier to set up CI/CD and then integrate with other tools.

In the free version, when a merge request is raised, there is no way to enforce certain rules. We can't enforce that this merge request must be reviewed or approved by two or three people in the team before it is pushed to the master branch. That's why we are exploring using some agents.

I have been using this solution for more than six months.

It seems stable.

I didn't find any scalability issues so far. We have around 50 members who use this solution. Around 20 of them use it on a daily basis.

One of my colleagues got in touch with them, and his response was that their technical support was not that great. The details that they provided for the question were not that great.

We also use GitHub. Earlier GitLab was more favored, but now GitHub has everything that is there in GitLab. If GitHub is offering more, then there might be chances of switching to that. I am not attached to either of these solutions. If things are working better for me in GitHub, I will move to GitHub.

It is simple. You just create one repo and then give access. It takes maybe 5 to 10 minutes.

Its price is fine. It is on the cheaper side and not expensive. You have to pay additionally for GitLab CI/CD minutes.

Initially, we used the free version. When we ran out of GitLab minutes, we migrated to the paid version.

I would recommend this solution to others. I would rate GitLab an eight out of ten.

We use GitLab in the new project for CI/CD, integration, and deployment.

You need to have a good knowledge of the product in order to use it.

I have been using GitLab for six months.

GitLab is a stable solution, and we haven’t faced any bugs.

Around 40 people are using the solution in our organization.

We previously used SVN and Jenkins. We switched to GitLab because it is an advanced tool with many new features.

The solution's initial setup is easy if you follow the official document.

We are using the free version of GitLab.

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.

We use Gitlab for CICD work. 

Git hosting has an integration with ACD which is why we liked this solution in the first place.

This solution could be improved by adding modifications such as slack notifications.

I have been using this solution for four years.

This is a stable solution. 

This is a scalable solution although the CICD may be tricky to scale. 

I have previously used Bit Bucket and Github. Bit Bucket has some issues in our country. At the time we had banning issues within our government and only GitLab was. Bit Bucket is too slow and we had to wait for five minutes just to enter the platform. 

Bit Bucket pipelines are not that easy to consider and it was harder to use than GitLab. Gitlab is also more customizable. GitHub is more expensive than GitLab and didn't offer CICD. 

The initial setup is straightforward. 

I would rate this solution a ten out of ten.