GitLab Reviews

My company's programmers use GitLab for everyday development purposes.

The solution's most valuable feature is that it is compatible with GitHub. The product's integration capabilities are sufficient for our small company of 35 people.

Some of the programmers in my company have had complaints about the product.

We do face issues in our company when we run out of disk space. We had to do some low-level system interventions to recover the server from GitLab in our company. It would be good if GitLab implemented some diagnostic features so that the server prevents functioning when it detects insufficient disk space. It is important to prevent cache to avoid running out of disk space. Considering the aforementioned details, making a recovery wasn’t simple.

I have experience with GitLab.

Stability-wise, I rate the solution a nine out of ten.

Owing to the small size of my company, we do not need to utilize the scalability feature of the product.

My company has around 20 users of the product.

The initial setup of GitLab was okay.

The setup phase was completed in a day.

Our company has DevOps and CI/CD to help us with the deployment process of the product.

Though I am unsure, I feel that the solution is deployed on-premises.

The deployment phase was carried out with the in-house members of our company.

Speaking about the pricing of the solution, my company uses GitLab Community Edition.

Before choosing GitLab, my company had considered Microsoft TFS during the evaluation phase.

GitLab is a product managed by the department of programmers in our company, and I am not much involved in it.

I recommend the solution to those planning to use it.

I rate the overall product a ten out of ten.

It is used for saving source code, and then people get the source code out of it, make a branch, and merge it to make a big file for deployment. So it's mainly a source code deployment tool.

GitLab is very well-organized and easy to use. Also, it offers most features that customers need. So I think it's one of the best solutions compared to other options. So, it's the most capable and easiest tool.

In terms of the solution's interface and features, I am satisfied.

As a partner, sometimes it's difficult to get support. They have a really complicated procedure for their support. Apart from the aforementioned reason, I am very satisfied with the product. It is only after we are registered that we get proper support from GitLab. The registration itself it's quite complicated, and it is mainly because they want to make sure that the users with a license contact the right support team.

I have been using GitLab for two years. My company has a partnership with GitLab. I am using GitLab Version 15.6.

It is a stable solution. Stability-wise, I rate the solution an eight or nine out of ten. Since it is software, they can have some bug-related issues, and no software is 100% protected. GitLab has many features in different areas, so I cannot specify which specific area has a problem.

It is a scalable solution. Scalability-wise, I rate the solution a ten out of ten. My clients who use the solution are medium-sized businesses.

The solution's technical support is good. I rate the technical support a ten out of ten. Only the initial registration is complicated.

Positive

The solution's initial setup process was easy. I rate the initial setup a ten out of ten. The solution can be deployed in a day. Only one engineer is required to deploy the solution. Also, the solution does require maintenance. Using it as a different storage operation when it comes to maintenance, there can probably be some updates that can fix security patches and other issues. So, we have several employees working on many different solutions and projects. But only one person is actually required for its maintenance.

Price-wise, it is a reasonable solution. On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing a five out of ten.

It's a great solution. So I would recommend it to those who want to use it. I rate the overall solution a ten 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 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.

For us, Gitlab's most valuable feature is the integration with Cypress. We're using Cypress as an automation tool, so we're using GitLab as a tool for running in parallel.

I'm new to GitLab, so I would appreciate more documentation about the code and commands.

I have been using GitLab for almost a year now.

I rate GitLab nine out of 10 for stability.

I rate GitLab eight out of 10 for scalability. We have around 40 people using it.

Setting up GitLab is straightforward. 

I believe we are using the free version of GitLab. 

I rate GitLab a solid nine out of 10. I recommend GitLab. Based on what I've heard, I think GitLab is will be the permanent tool we'll use. I don't think that we're going to look for any other tool in the near future.

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.

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. 

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.