GitLab Reviews

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.

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. 

We are providing solutions for consumer electronics. We have a repository of our code between the device team, mobile applications team, and cloud team.

It is very useful for code reviews and merging operations. Review analytics is available to users with reporter access and displays a table of open merge requests. Many merge requests can be added to the train. Each merge request runs its own merged results pipeline, which includes the changes from all of the other merge requests. If the pipeline for a merge request fails, the breaking changes are not merged, and the target branch is unaffected. It is very useful for merging our code and tracking another branch before giving release. Its interface is straightforward to see all process.

It can be free for commercial use of project management and code integrity features.

I have been using git solutions for almost two years. We are new for GitLab.

It is stable.

We are a small team. Almost 60 people are working on the same repo. It works for us currently, and we don't need to scale it.

For any technical issues, we have our infrastructure team. They have some experience with this product. Currently, we don't create any tickets for technical operations.

We were using Subversion. GitLab is a little bit more complex than Subversion, but it is okay for me.

It is easy.

We have an IT department for infrastructure operations, and they are managing this solution for us.

It seems reasonable. Our IT team manages the licenses.

I would advise others to follow best practices because they are useful for each case. If you have a problem, it can be easily solved by other people if you follow the best practices.

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

I've used the solution just for my learning purposes. My company is using currently GitLab. We are using it for our CI/CD purposes for continuous integration and continuous deployment.

To my knowledge, my company started to use it as there were no decent alternatives to GitLab when they started to use it. The only decent alternative was GitHub, however, it was lacking in the CI/CD pipeline capabilities. At that time there were no GitHub actions available at the moment.

Of all available products, it was the easiest to use and easy to install.

The solution should be more cloud-native and have more cloud-native capabilities and features. It should be more GitOps-ready.

I started using the solution a year ago. My company has used it for four years.

I cannot speak to how stable the solution is. From what I have seen so far, there were no serious issues with GitLab.

Approximately four to five developers and maybe a couple of QA testers and a couple of DevOps engineers are responsible exclusively for GitLab maintenance and support.

Technical support has mostly been good.

Positive

I tried to learn a little bit about Jenkins, however, it was only through some internet content.

At the moment of the GitLab acquisition, I was not working for the company. I did not handle the implementation process.

We need at least a couple of technicians, engineers, for deployment and maintenance. 

Our own technical team handled the deployment. 

When I was hired (in 2020) they told me that they were using an open-source version. I'm not sure if that's still the case as it's a quite big company. Nowadays they should be using some kind of paid version, as the demand is pretty high, as far as I know.

I'm not sure of the exact licensing costs. 

We are customers and end-users.

As far as I know, we are using the on-premise version. There are two versions of GitLab - the on-premise and the cloud version. We are using on-premise. As far as I know, we also keep making sure it's up-to-date.

I'd rate the solution nine 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.

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 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.