GitLab Reviews

We are using the product for configuration management and source course management. For some projects, we are using it issue management.

Configuration and source management are the most valuable aspects of the solution.

It offers an easy initial setup. 

The solution is stable.

I find the product scalable. 

It's not overly expensive. 

We'd always like to see better pricing on the product. If they could make the cost lower, that would be ideal for users. 

We've been using the solution for five or six years. 

The solution is stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

It is scalable and easy to expand. 

We have about 100 users on the solution. That includes developers and testers. 

Our team is getting better. We'll likely need 30 more licenses. Therefore, we plan to expand usage.

We don't need technical support. Our IT team has handled all the issues and therefore we don't need any additional support.

We did previously use a different solution. I can't recall the name.

The solution is very straightforward to set up. It's not very complex at all. My understanding is it quite easy to implement. However, I was not completely involved. 

We pay a yearly licensing fee. The pricing is pretty low. It's not too expensive. 

We did not evaluate other solutions. We've always used GitLab.

I'm not sure which version of the solution I'm using. 

I'd rate this product nine out of ten.

My team primarily uses GitLab for CI/CD purposes. Whatever code I develop has to go with the team, so I work in a team that tries to write its version of the code, or uses the ticketing system, takes a ticket, covers that information, and then updates the main branch about it. That's the use case my team has for GitLab.

We're only using the basic features of GitLab and haven't used any advanced features. The solution works fine, so that's what we like about GitLab. We're party using GitHub and GitLab. We have a GitHub server, while we use GitLab locally or only within our team, and it works okay. We don't have any significant problems with the solution.

We also found the straightforward setup, stability, and scalability of GitLab valuable.

I've noticed an area for improvement in GitLab, particularly needing to go through many steps to push the code to the repository. Resolving that issue would make the product better.

My team quickly fixed it by writing a small script, then double-clicking or enabling the script to take care of the issue. However, that quick fix was from my team and not the GitLab team, so in the next release, if an automatic deployment feature would be available in GitLab, then that would be good because, in Visual Studio, you can do that with just one click of a button.

I've been using GitLab for almost four years.

As of now, we don't have any issues with GitLab stability-wise. We never faced any critical issues, so everything's going smoothly.

GitLab is a scalable solution.

We didn't use the technical support for GitLab because there are specific people within our organization that we can contact about issues, for example, access issues or permissions, and they give us access to the folders.

We haven't used any other build automation product other than GitLab.

We found the initial setup for GitLab very straightforward. We're developers, so we develop the code, then push that code to our branch. We have a moderator who keeps track of the testing process, so from our side, we already have the steps and what needs to be done and written, so we follow those steps to set up GitLab.

The implementation of GitLab was done in-house within my company.

As I work in a vast enterprise, I'm unsure about the licensing cost for GitLab. It's the management team that takes care of that.

I'm a developer, so I write all the code from scratch, but I don't use predefined platforms. I've been using GitLab and Visual Studio, though.

As GitLab is only used within my team, only five people use it.

My team uses GitLab almost every day, then when a project is complete, my team pushes it back into GitHub.

My team is an end-user of GitLab.

Regarding recommending GitLab to others, I'm a developer of data science solutions, so I mostly do end-user tasks rather than developer tasks. As of now, nothing was so bad about GitLab, and I didn't come across any significant hardships in using the solution. For a person like me who uses resources in a bigger enterprise, there shouldn't be problems using GitLab. If you're part of a small company, there could be some issues.

My rating for GitLab is seven out of ten.

We are using GitLab for code management. We put code onto their servers. This allows developers to have a centralized place for code collaboration.

GitLab has helped our company save time. In our current project, we have split the job into two parts, one team is working on one particular feature and when done the solution merges the code together. Every two weeks we can release a new APK. We have the latest code in development so we don't need to merge code manually.

The solution receives frequent updates, it is always improving.

The most valuable feature of GitLab is the automatic merging of code.

I have been using GitLab for approximately seven years.

GitLab is highly stable.

The scalability of GitLab is good.

All developers are using GitLab in my company.

I plan to increase the usage of the solution in the future.

I rate the support from GitLab a four out of five.

Positive

I have previously used Bitbucket and Filezilla.

The initial setup of GitLab is easy.

There are different licensing options available, including a free limited-user license.

We evaluated other options before choosing GitLab.

One person can do the maintenance of the solution.

My advice to others is for them to use GitLab for managing their code.

I rate GitLab a nine out of ten.

During the development environment, we have a different number of developers, close to five. So each of them will have a different project. Maybe some of them do it in one project, but their assignment or the activity they are doing may be different, so they will do their activity and then they will push it to the GitLab. If there is an amendment or update required, they will pull it from GitLab and if they do their activity again, they will push it. 

GitLab also does the merging . The merging feature makes it easy later on for the deployment.

I would like to see security increased in the future. A secure environment is very important.

I have been using GitLab for the past seven years.

The cloud provides good stability for GitLab.

GitLab is scalable. I think they have their own actually premium services. So, there are some functionalities and features that may be added on top of the free version.

The initial setup of GitLab is easy and straightforward. You do not need to be a deployment expert. It can be done by the managers or directors. 

GitLab can be done in-house but we are using CloudWatch. All you need is to have a free account.

The initial setup cost is excellent and you can add the premium features later.

Using GitLab is important to help provide a more secure and reliable environment for developers working with information in the cloud. GitLab brings a level of safety. I would rate GitLab a ten out of ten.

GitLab's best features are continuous integration and fast deployment.

GitLab's UI could be improved. In the next version, the documentation of the migrations steps should be better.

I've been working with GitLab for six years.

GitLab is very stable.

GitLab is scalable.

GitLab's technical support is quick and responsive.

Positive

The initial setup is pretty simple for GitLab as a service, but it's more complex for a hosted solution.

GitLab is comparatively expensive, but it provides value because it's feature-rich. I would rate its pricing four out of five.

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

GitLab is for professional teams, and it has some abilities in the user interface that are interesting to me. 

The look of the user interface is good. I have seen many features here that I don't see in BitBucket.

We like the automatic deployment for different environments. For example, if you want to deploy your application for the Azure system, Azure Cloud, you have the default configuration for them. That's true for Amazon or a VM, for example, as well. 

They provide default templates for products.

It is an easy setup.

The solution is stable.

It scales well.

I have a free version. It is open-source.

Authentication can be a problem when you have an application and you want to configure it with them. I used Spring Cloud config and to connect that to GitLab was so hard. It took hours for me to configure that.

I've been using the solution for two years. 

The product is perfectly stable. There aren't bugs or glitches. It doesn't crash or freeze. 

The solution is scalable. It easily expands. 

I have two projects. In my personal experience, for my own project, it's a scalable system for e-commerce mobile microservice spaces for event-driven e-commerce systems that are using GitLab.

I've never requested the assistance of technical support.

I'm also familiar with Bitbucket, although I don't use it right now. 

The solution is quite simple to set up. 

I'm actually proficient. I'm not sure if a beginner user would have issues. It's likely okay for them.

The only difficult part may be the authentication configuration. It's a specific thing and not very common. 

I didn't use an integrator. It is easily deployed in-house. 

I don't need a license. I use the free version, and that is perfectly fine for me. 

I always use the latest version of GitLab. I don't check the version number.

I'd recommend the solution to others. 

I'd rate it a ten out of ten. I'm happy with its capabilities. 

The most valuable functionality of GitLab, for me, is the DevOps. Besides the normal source control based on Git, I find the Auto DevOps features most important in the solution.

As GitLab is not perfect, what needs improvement in the solution is the Wiki feature of the groups or the repertories because currently, it's not searchable by default. You'll need an indexing service such as Elasticsearch to make it searchable, and that requires too much work, so for me, it's the main feature that should be improved in GitLab.

In the next version of the solution, from the top of my head, the documentation could be improved. Besides the Wiki, it would be good if there's documentation that would be automatically generated based on the code repository. In other words, there should be some tutorials from GitLab for developers in the next release.

I've been using GitLab for almost three years.

GitLab is a pretty stable solution, and on a scale of one to ten, with one being the worst and ten being the best, I'm rating its stability a ten. My team just learned some details about the configuration of GitLab, so it's now tuned up, and right now, there's no problem with the stability of the platform.

In terms of GitLab scalability, based on its features, it's supposed to scale easily enough geographically, but my company hasn't tried scaling it yet. It shouldn't be a big problem to scale the solution.

In terms of the technical support for GitLab, I mainly use the forums and support sites of the solution. I don't use the direct technical support line of GitLab.

The initial setup for GitLab is simple mainly because of all its features that allow you to make a startup instance of the solution simpler and quicker, and that's very good.

In terms of the pricing for GitLab, on a scale of one to five, with one being expensive and five being cheap, I'm rating pricing for the solution a four. It could still be cheaper because right now, my company has a small team, and sometimes it's difficult to use a paid product for a small team. You'd hope the team will grow and scale, but currently, you're paying a high license fee for a small team. I'm referring to the GitLab license that has premium features and will give you all features. This can be a problem for management to approve the high price of the license for a team this small.

We evaluated Azure DevOps, but we liked the style of how things are built up inside GitLab for the end-user and the developer more compared to Azure DevOps, though Azure DevOps is also a very good choice.

I'm using the latest version of GitLab.

My company has a small team and only has six users of GitLab.

On a scale of one to ten, where one is the worst and ten is the best, my rating for GitLab, in general, is nine. My company likes the solution very much, especially over Azure DevOps.

I would recommend GitLab for others to use.

My company is a customer of GitLab.