GitLab Reviews

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.

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. 

We use it for version control and CI/CD.

CI/CD is very good. The version control system is also good. These are the two features that we use.

Its security features are very expensive. The Ultimate version is very expensive.

I would like more Agile features in the Premium version. The Premium version should have all Agile features that exist in the Ultimate version. IBM AOM has a complete Agile implementation, but in GitLab, you only have these features if you buy the Ultimate version. It would be good if we can use these in the Premium version.

I have been using GitLab for five years.

It is very stable. In five years, we had to fix it only once.

It is very scalable. We have about 2,000 users, but as per the reference architecture documentation, it can be scaled up to 50,000 users.

We are using the open-source free version. So, we don't have support. We are looking to buy the intermediate version or Premium version. 

It was very easy to set up. 

We set it up by ourselves. We also update it, and we don't have to turn it off.

We are using its free version, and we are evaluating its Premium version. Its Ultimate version is very expensive.

We are evaluating its Premium version, and we are also evaluating other products like GitHub.

I would rate it a nine out of 10.

We are using it for pipelines, continuous integration, and continuous deployment. 

In terms of deployment, it can be a cloud solution, but we have installed it on our site on Azure.

GitLab is very useful for pipelines, continuous integration, and continuous deployment. It is also stable.

Its price should be improved. It is very expensive.

Based on what I know so far, its integration with Kubernetes is not so good. We have to develop many things to make it work. We have to acquire third-party components to work with Kubernetes. 

From the DevOps perspective, the way we deploy applications is too complicated. It needs to be simplified. It is very development-oriented, and it works very well for DevOps, but when you are at the group level, you want it to be simple and more oriented towards the process. The automation process to deploy is not a very good part of GitLab.

I have been using this solution for three or four years.

It is stable.

Its scalability is fine. We have 200 developers in our organization. 

We have been doing okay on our own. We are able to find support inside our company.

Its initial setup is okay. We did the installation in three months, but it was very slow and complicated to develop the continuous deployment during these three years for each application. We had to develop pipelines for multiple development languages.

We are quite well organized now, but it took a long time to think about which pipeline to use with GitLab. We now have five pipelines. We have the infrastructure pipeline, the middleware pipeline, the image pipeline, the security pipeline, and the application pipeline.

We have a team of 10 people for its deployment. They are admins and managers.

It is very expensive. We can't bear it now, and we have to find another solution.

We have a yearly subscription in which we can increase the number of licenses, but we have to pay at the end of the year. 

We are using the Azure Cloud solution, and we are thinking of trying the Azure DevOps solution this year. 

I would recommend this solution to others. The product is fine, but you have to do the integration with different pipelines.

I would rate GitLab a seven out of 10.

We are using it for building mobile applications and web applications. I am supporting the code in GitLab. It is only for giving access to my development team, and I just see what merge requests are coming.

I like GitLab from the CI/CD perspective. It is much easier to set up CI/CD and then integrate with other tools.

In the free version, when a merge request is raised, there is no way to enforce certain rules. We can't enforce that this merge request must be reviewed or approved by two or three people in the team before it is pushed to the master branch. That's why we are exploring using some agents.

I have been using this solution for more than six months.

It seems stable.

I didn't find any scalability issues so far. We have around 50 members who use this solution. Around 20 of them use it on a daily basis.

One of my colleagues got in touch with them, and his response was that their technical support was not that great. The details that they provided for the question were not that great.

We also use GitHub. Earlier GitLab was more favored, but now GitHub has everything that is there in GitLab. If GitHub is offering more, then there might be chances of switching to that. I am not attached to either of these solutions. If things are working better for me in GitHub, I will move to GitHub.

It is simple. You just create one repo and then give access. It takes maybe 5 to 10 minutes.

Its price is fine. It is on the cheaper side and not expensive. You have to pay additionally for GitLab CI/CD minutes.

Initially, we used the free version. When we ran out of GitLab minutes, we migrated to the paid version.

I would recommend this solution to others. I would rate GitLab an eight out of ten.

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

The solution's most valuable features are pipelines. GitLab allows you to automate things and show them diagrammatically.

The solution is much harder to get around and organize extra features. It has fewer options, and its UI is not so user-friendly.

I have been using GitLab for one year.

GitLab is a very stable solution.

I rate the solution’s stability an eight out of ten.

I rate the solution’s scalability a seven out of ten.

Although the solution's documentation is publicly available, you have to invest much more time to read everything and understand how to get around.

On a scale from one to ten, where one is very easy and ten is difficult, I rate the solution's initial setup a six to seven out of ten.

The solution's pricing is acceptable.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a six out of ten.

I got familiar with the CI part of the tool. If you want to use all the features for testing and packaging, you have to use the paid version.

Overall, I rate the solution a six out of ten.

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.

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.