GitLab Reviews

GitLab can be deployed on-premise and in the cloud.

GitLab is mainly used as a repository.

The most valuable feature of GitLab is the ability to upload scripts and make changes when needed and then reupload them. Additionally, the solution is user-friendly.

I have not explored the solution fully but the features that I have used have been good.

GitLab can improve the integration with third-party applications. It could be made easier. Additionally, having API control from my application could be helpful.

I have been using GitLab for approximately three years.

The stability of GitLab is good.

We have approximately 20 people in my department using GitLab and in my organization, we have approximately 4,000 people using it.

I have not used the support from GitLab.

The initial setup of GitLab is complex and could improve.

GitLab is an open-source solution.

I rate GitLab a nine out of ten.

The deployment and performance of GitLab could be better. In addition, the solution could be faster.

We have been using this solution for more than five years, and it is deployed on cloud.

GitLab is stable.

It is a scalable solution.

The installation was straightforward.

I rate this solution a seven out of ten, and it is good for a small set of people.

GitLab is being used as a repository for our codebase and it is a one stop DevOps tool we use in our team.

GitLab has repository and deployment features that are integrated into one solution. This is its most valuable feature.

It is a little complex to set up the pipelines within the solution.

We have been using this solution for two and a half years. 

This is a stable solution. 

This is a scalable solution. 

I have used several tools like Ansible for deployment and Nexus as a repository. We moved to GitLab because these features are integrated into one solution

The initial setup is quite complex. The time it takes to deploy the solution depends on the artifacts. We have several steps in our pipeline so it usually takes around four to five minutes for the pipeline to complete.

We are using the Community Edition and this is free.

It takes some time for the environment to become stable once you migrate from another solution.

I would rate this solution an eight out of ten. 

I primarily use GitLab for maintenance and deployment of projects.

GitLab's best features are maintenance, branch integration, and development infrastructure.

I've been using GitLab for two to three years.

GitLab's stability is almost always good, but it depends on your connection with the network. If the GitLab services are running properly, and your services and network are fine, then there shouldn't be any problem with stability. There are some wrinkles, but they're around 5-8% and are mostly contained.

Previously, I used Team Foundation Server (TFS).

The initial setup was quite challenging because it takes some time to understand how to pull out or push the code.

GitLab is a very good solution because you can completely maintain your code and have a number of developers working on the same project. I would recommend GitLab for those doing technology development, and I'd give it a rating of nine out of ten.

We use this solution for storing repositories for distributed programming. We have 15 to 20 users. We generally keep our POC repositories on GitLab.

As a developer, this solution is useful as a repository holder because most of the POC projects that we have are on GitLab. 

GitLab's Windows version is yet not available and having this would be an improvement. This is compared to Azure Git where Microsoft provides us with the setup of virtual agents which you can download and set up quickly. Your laptop will become an agent which is connected to your cloud environment to execute the job which is triggered from the cloud environment. 

I've been using GitLab as a developer for four to five years, but when it comes to practical implementation in my current organization, it's been about a year since we started shifting our repositories to this platform.

Absolutely, the solution is stable and satisfies our requirements. 

Due to the relatively small number of users in our organization, I can't really comment on the scalability of this solution. 

We have never needed to contact customer support. Whenever we had an issue, all the help we needed for a solution is on the platform or in the documentation.

We used to use TFS repositories on the older versions of Microsoft.

I have done a setup on-premise for GitLab and it was straightforward. The documentation is clean which is useful for the DevOps person who sets up the on-premise environment. Based on the documentation provided by GitLab, I have prepared my own documentation.

To complete the deployment, it took me two to three days including downloading the artifact from the internet, getting the Linux server ready and setting up GitLab runner for CI/CD. I was the only person involved in the setup and we have 15 to 20 total users across our organization, almost all of them developers. 

I rate this 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.

We were working on our pipeline infrastructure running GitLab and we needed some scripts, such as Terraform, to complete some operations.

I have found the solution has good performance.

The solution could improve by having better integration.

I have been using GitLab for a couple of weeks.

The solution is stable.

The stability of the solution has been good.

I was satisfied with the support.

There is a license required for this solution.

I have evaluated Slack.

I would recommend this solution to others.

I rate GitLab a seven out of ten.

We use GitLab for the continuous deployment of CI/CD pipelines that are running on various GitLab services. We also use it to run nightly jobs and to run any other case-specific issues.

I like that it's easy to deploy our services over GitLab. The customer support is also good with a really active community. You have a lot of support that you can get online with your stack. That is probably one of the benefits of using GitLab. It's also really fast.

It would be better if there weren't any outages. There are occasions where we usually see a lot of outages using GitLab. It happens at least once a week or something like that. 

Whatever pipelines you're running, to check the logs, you need to have a different set of tools like Argus or something like that. If you have pipelines running on GitLab, you need a separate service deployed to view the logs, which is kind of a pain.

If the logs can be used conveniently on GitLab, that would be definitely helpful. I'm not talking about the CI/CD pipelines but the back-end services and microservices deployed over GitLab. To view the logs for those microservices, you need to have separate log viewers, which is kind of a pain. 

I have been using GitLab for over a year.

GitLab is a fairly stable solution. On a scale from one to ten, I would give it a seven for stability.

GitLab is scalable. You can replicate services, architecture, and more.

Technical support is good.

I would recommend this solution.

On a scale from one to ten, I would give GitLab an eight.