GitLab Reviews

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.

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.

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.

I'm part of the application development team comprising 10-12 developers and I have used GitLab for configuration and version management. We have also used it for DevOps, but I have not been involved in the DevOps side. My work with GitLab involved basic version management (i.e. checking in, checking out, merging) and related features. 

I have also used GitLab for doing remote builds, which is when you check in and it triggers the build on the application remotely. For example, we have a YAML script that has been written for performing builds on GitLab automatically and when that script gets executed, it performs the builds and copies them to the destination folder. All of this gets triggered from GitLab.

I like that you can use GitLab as a double-sided solution for both DevOps and version management. It's a good product for working in these two areas, and the user interface makes it easy to understand.

There was a problem with the build environment when we were looking at developing iOS applications. iOS build require Mac machines and there are no Mac machines provided by GitLab in their cloud. So to build for mobile iOS application, we needed to use our own Mac machine within our own infrastructure. If GitLab were to provide a feature such that an iOS application could also be built through GitLab directly, that would be great.

I have used GitLab for two months.

It's stable. 

Once all the scripts are written, it becomes scalable. When an application gets deployed and people start using it, it's on the cloud and so it becomes scalable. All the applications that we design are deliberately written in such a way as to be scalable.

We only used GitLab for a short duration, so there was not much scope or need for contacting technical support.

The setup is straightforward to an extent because the part of GitLab that I was using for version management was similar to other tools that I have used such as Git and SVN. When I use GitLab, it's more or less the same process and workflow as these other tools, so there wasn't a big learning curve for me.

Our application was an accumulation of multiple applications, so there were multiple builds happening at any given time. GitLab would process the builds and it would take only a couple of hours for us to deploy the builds on the cloud.

The other thing is that the GitLab user interface is good, so it's easy to understand. You, yourself, can learn it simply by exploring and trying it out. Then there's a lot of help that is available on the GitLab website on how to use it. 

For the implementation, we had a DevOps engineer who was the primary technical guy, and then the others were developers and related entities performing the development.

Personally, I can't say much about the return on investment because the licensing and costs and everything have been borne by our customer. We were just using it. But I think that the return on investment must be good, and it might be one of the reasons why the customer is using it for all their projects.

I'm not aware of the licensing costs because those were covered by the customer.

I can certainly recommend GitLab. It's a good product and I would rate it an eight 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.

I work in PMO, and I standardize the workflows for scrum teams, AI teams, and kanban teams. If I have some scripting in Jira, and I need to save it in GitLab.

It is our source-code repository. It's used for the BI process, continuous integration, and continuous development. It's used for DevOps people. All of our IT people use GitLab.

The source-code repository is great. 

I really like the pipelines.

The stability is good. 

We'd like to see better integration with the Atlassian ecosystem. There needs to be better and native integration. That is really useful for us as Atlassian Jira has strong integration with Bitbucket, and Bitbucket is a computation of GitLab.

We've used the solution for a long time. I've used this solution for one year at this company. However, I've used it for five or eight years. 

The solution is always working. I haven't experienced problems with GitLab.

My company is 100 people, however, my instance of IT people has 10,000 people in Jira. I work with a lot of developers.

I've never used technical support. I can't speak to how helpful they are. 

We changed Bitbucket for GitLab.

I'm not the main of GitLab. I did not initially set up the product.

We've likely seen an ROI. 

I don't deal with any licensing aspects of the solution. I can't speak about the exact costs. 

We are customers and end-users. 

I'd rate the solution an eight out of ten. 

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.