GitLab Reviews

I am using GitLab for code management, such as code cloning, and code-to-data.

The most valuable feature of GitLab is its convenience. I am able to trace back most of my changes up to a far distance in time and it helps me to analyze and see the older version of the code.

The user interface could be more user-friendly. We do most of our operations through the website interface but it could be better.

I have been using GitLab for approximately three years.

I rate the stability of GitLab an eight out of ten.

I rate the scalability of GitLab an eight out of ten.

We have more than 1,000 developer users using this solution in my organization.

We have an internal administrator if we need help with the solution, I have not contacted GitLab for support.

I have used previously CVS. Both CVS and GitLab have their advantages and disadvantages. GitLab is in the cloud and can be accessed anywhere which is very flexible. For the functionality, I am not certain about the differences. I find them both to be good solutions.

I would recommend this solution to others that are doing code management.

I rate GitLab a seven 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. 

Our company uses the solution to manage code, Wiki, and repository management for multiple projects on Truck It In. The solution helps us manage our experience with projects. We currently have twenty-two developers using the solution.  

We are in the process of executing the pipelines to use the solution for CI/CD. 

The interface is much more user friendly than competitor products. 

The merge request tool is very valuable. 

It is easy to perform code and peer reviews. 

Key features allow creation of well-presented Wiki that includes ideas, development, and domains. 

The solution should expand features to match other tools such as Coverity, Veracode, or SonarQube with its static code analysis tool so third-party integrations are not required.

There can be a lapse of fifteen minutes to a day when updates are pushed. We do receive email notification of upcoming lapses and push progress, so that helps.

I have been using the solution for eight months. 

The solution is stable with no failures or issues in the version controlling or epic creation processes. 

The solution is scalable. We can manage issues or epics, make Kanban with proper backlog, and move any processes with no problems. It is scalable in terms of managing our experience and using it as a project management tool. 

We have not needed technical support. 

The setup is straightforward with good user interface. Third-party integrations can be a bit of a hassle. 

We implemented the solution in-house. 

We use Spring Boot at the back end with IntelliJ for IDs. IntelliJ is a good tool that integrates our projects with the solution through a well-managed synchronization process. 

The solution has a better user interface than GitHub and Bitbucket. 

We also use ClickUp which is a great tool for managing tickets and stream planning. We follow Agile methodologies so ClickUp is quite helpful to us. 

SonarQube has a new integration with the solution so we use its static code analysis tool.

The solution is valuable for developers because it includes version controlling, pipelines, CI/CD, and integrations. When moving from the development side to the production side it is important to ensure that code is bug-free with no errors. We have less issues on the production side because we take full advantage of the solution. 

The solution currently requires third-party integrations for CI/CD so I rate it a seven out of ten. 

Because GitLab uses an education license for cloud, there is unlimited storage for each account, so it's very useful. It is very flexible and easy because you can store data on cloud.

GitLab should include more features because, during the pandemic, companies like Google introduced more features. The integration and storage capabilities could be better. This would be very handy for educators and students.

We used this solution at my previous company for a few years. They initially deployed it on-premises but fully migrated to cloud because all the data was not fully backed. We had around 500 clients and 500 accounts.

It is 100% stable.

I believe it's scalable. It is suitable, and there was no need for exploration.

We used a lot of technical support for standard settings.

It is subjective. I cannot compare GitLab with Azure because it is based on experience.

We had to read the manuals first before we could set up. The manuals are helpful for consultants as we needed their expertise to complete the setup. In addition, they can ensure there is no downtime.

It has a very good price and is good for general sidetracking.

I rate this solution a ten out of ten.

I am using GitLab for many purposes, such as CI/CD.

I have found the most valuable features of GitLab are the GitClone, GitPush, GitPull, GitMatch, GitMit, GitCommit, and GitStatus.

GitLab could improve by having more plugins and better user-friendliness.

I have been using GitLab for four years.

GitLab is a stable solution based on version control.

The scalability of GitLab is good. We can have multiple Amazon AWS enrollments.

We have approximately eight people using this solution in my company.

We use the support when we are doing integration. We have a blog where we can open a ticket and receive support.

The initial setup of GitLab is easy. If there is a server the implementation will take 30 minutes to one hour. In the case, there is no server, then we can install the Docker box with the related supporting office installation. This will take approximately two hours.

This is an open-source solution.

We are using this solution because of our client's requirements.

I would advise others to prepare the documentation for their team members.

I rate GitLab a nine out of ten.

The solution is cloud-based. There are around 30 people using this solution in my organization. 

GitLab is kind of an image of GitHub, so it gives us the flexibility to monitor our changes in the repos. Multiple people can work on the same code and make various branches. We can merge them together and resolve conflicts. This feature makes development quite fast. Everybody gets to work on their own feature independently without waiting for someone else to complete their code first.

When deploying the solution on cloud and the CI/CD pipeline, we have to define the steps and it becomes confusing. The trend is shifting toward CI/CD pipeline automation, so GitLab could provide some features that help with CI/CD automation. 

There could also be integration with different cloud services like GCP, AWS, or Microsoft Azure. A one-click deployment with the CI/CD pipeline of our code would be a good feature.

I worked with GitLab for one year.

The solution is stable. We haven't encountered any issues with loading repos.

It's scalable. We haven't performed a lot of computation on GitLab because we're just storing our code on it. We can create as many admins, branches, and projects as we want.

I haven't contacted technical support because we haven't encountered any issues. 

Initial setup is simple. Our model and other application repo was pushed on GitLab. From there, we pushed the code into the VM and then used that to make the Docker images. The models were deployed on GCP. It was easy to deploy them on Cloud Run on GCP.

The solution isn't as expensive as other solutions.

I would rate this solution as nine 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.

I use GitLab to bring code from repositories.

GitLab's best feature is Actions.

GitLab would be improved with the addition of templates for deployment on local PCs.

I've been using GitLab since 2019.

GitLab is stable, I would rate its stability nine out of ten.

Previously we used Team Foundation Server, but GitLab is better for local cloud deployment.

The initial setup was simple.

GitLab is highly priced for smaller teams, but it's okay if considering a user base of thousands.

I would give GitLab a rating of 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.

Most of the features are pretty good.

The code merging capability is something that we use very frequently. Merging code is a big factor for us because most of our teams use GitLab.

The integration could be slightly better.

The interface should be more user-friendly.

We have been working with GitLab for more than five years.

It is a stable product. We have not had any issues with respect to instability.

With approximately 30 users, we are not a large company. I found the scalability to be okay but I haven't tested it extensively.

We have experience with GitLab support and we found the service to be good. There is not much of a lag in terms of addressing queries.

I would rate the support a five out of five.

Positive

I also use GitHub and I am more comfortable with GitLab.

The initial setup is simple.

This product is not very expensive but the price can be better. As such, I would rate GitLab a four out of five in terms of pricing.

Overall, this is a good product that has a lot of features. There are several features that I don't use personally but other members of my team do.

I would rate this solution a nine out of ten.