Coming October 25: PeerSpot Awards will be announced! Learn more
Product Development Team Lead R&D at a tech vendor with 1,001-5,000 employees
Real User
Web-based repository used for distributed programming and to store POC repositories
Pros and Cons
  • "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."

What is our primary use case?

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

What is most valuable?

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

What needs improvement?

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. 

For how long have I used the solution?

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.

Buyer's Guide
GitLab
September 2022
Learn what your peers think about GitLab. Get advice and tips from experienced pros sharing their opinions. Updated: September 2022.
632,779 professionals have used our research since 2012.

What do I think about the stability of the solution?

Absolutely, the solution is stable and satisfies our requirements. 

What do I think about the scalability of the solution?

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

How are customer service and support?

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.

Which solution did I use previously and why did I switch?

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

How was the initial setup?

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. 

What other advice do I have?

I rate this solution an eight out of ten. 

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Gizem Mercan - PeerSpot reviewer
Cloud Architect at a manufacturing company with 10,001+ employees
Real User
Top 20
Good interface, stable, and useful for merge operations and reviews
Pros and Cons
  • "It is very useful for reviews. We are using branch merging operations and full reset operations. It is also very useful for merging our code and tracking another branch. The graph diagrams of Git are very useful. Its interface is straightforward and not too complex for us."
  • "It can be free for commercial use."

What is our primary use case?

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

How has it helped my organization?


What is most valuable?

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.

What needs improvement?

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

For how long have I used the solution?

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

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

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

How was the initial setup?

It is easy.

What about the implementation team?

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

What's my experience with pricing, setup cost, and licensing?

It seems reasonable. Our IT team manages the licenses.

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
GitLab
September 2022
Learn what your peers think about GitLab. Get advice and tips from experienced pros sharing their opinions. Updated: September 2022.
632,779 professionals have used our research since 2012.
UAS Innovation Group Lead at a computer software company with 11-50 employees
Real User
Top 20
Promotes collaboration, easy to use, and always evolving with the market needs
Pros and Cons
  • "This product is always evolving, and they listen to the customers."
  • "It would be really good if they integrated more features in application security."

What is our primary use case?

We use this solution for source code management, and also team collaboration for the application lifecycle.

How has it helped my organization?

It has improved the way our organization functions.

What is most valuable?

It is very easy to use.

This product is always evolving, and they listen to the customers.

It solves what the customers what.

What needs improvement?

It would be really good if they integrated more features in application security.

I would also like to see scanning for some vulnerabilities and allow people to have a one-stop glance at the state of the security application

For how long have I used the solution?

I have been working with GitLab for more than five years.

We are always using the latest version.

What do I think about the stability of the solution?

It's stable, and we have not experienced any issues with bugs or glitches.

What do I think about the scalability of the solution?

It's a scalable solution. It's easy to scale.

Which solution did I use previously and why did I switch?

We have used many solutions before GitLab.

How was the initial setup?

The initial setup is straightforward.

What's my experience with pricing, setup cost, and licensing?

The price is okay.

What other advice do I have?

My advice is to work on the processes that are in the environment. Know what you need to do and what you need to deliver the software. You have to ask the question: What do you need to deploy the software?

Always take security into account from the beginning.

While this is a good tool that is always evolving and there are new updated security standards that are being published and improved upon, it is always a good idea to have another solution to compare with to get better at using it. You can always have a combination of all of them, which would something that I would be interested in.

We are always evaluating to see if there is a solution that can do the job better.

You need to have a well-defined set of processes and that will help them adapt GitLab.

Overall, it's a great product and it does a good job.

I would rate this solution an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Alexandru Zeevleanu - PeerSpot reviewer
DevOps Team Lead at a tech services company with 501-1,000 employees
Real User
Beneficial YAML plans, reliable, and low maintenance
Pros and Cons
  • "The most valuable features of GitLab are the review, patch repo, and plans are in YAML."
  • "GitLab could improve the patch repository. It does not have support for Conan patch version regions. Additionally, better support for Kubernetes deployment is needed as part of the package."

What is our primary use case?

We use GitLab as a source code repository, terraform modules repository, generic packages repository and for our CI/CD pipelines.

What is most valuable?

The most valuable features of GitLab are the merge request approvals, package repository, and that GitLab CI/CD pipelines plans are written in YAML.

What needs improvement?

GitLab could improve the package repository. It does not have support for Conan packages revisions.

Additionally, better support for deploying GitLab in Kubernetes is needed (i.e. more mature helm packages and updated documentation).

For how long have I used the solution?

I have been using GitLab for approximately five years.

What do I think about the stability of the solution?

The stability of GitLab is good.

What do I think about the scalability of the solution?

GitLab is scalable. We only needed to add more resources to the VM. Horizontally, we were not able to scale it because we couldn't deploy it in Kubernetes correctly.

We have approximately 300 people using the solution in my organization.

How are customer service and support?

I have not used the support from GitLab.

Which solution did I use previously and why did I switch?

I previously used Gerrit and I prefer GitLab. It is much better in the interface and integration, it is much more than only Git software, it is more of a complete package.

How was the initial setup?

The initial setup of GitLab is not complex. However, it can be difficult to deploy GitLab on Kubernetes.

What about the implementation team?

The deployment of GitLab was done in-house.

What's my experience with pricing, setup cost, and licensing?

The solution's standard license is paid annually. They have changed the pricing tiers and removed the bronze tier, which was the perfect sweet spot.
There is a free version available.

I rate the price of GitLab a seven out of 10.

What other advice do I have?

I would recommend the solution to others. For a self-hosted version, I advise others to deploy it using Docker/Docker-compose, it is the easiest way. The solution has no maintenance. 

I rate GitLab a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
SCRUM Master at a retailer with 10,001+ employees
Real User
Top 5Leaderboard
Reliable with an excellent source-code repository and useful pipelines
Pros and Cons
  • "The stability is good."
  • "We'd like to see better integration with the Atlassian ecosystem."

What is our primary use case?

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.

What is most valuable?

The source-code repository is great. 

I really like the pipelines.

The stability is good. 

What needs improvement?

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.

For how long have I used the solution?

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. 

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How are customer service and support?

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

Which solution did I use previously and why did I switch?

We changed Bitbucket for GitLab.

How was the initial setup?

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

What was our ROI?

We've likely seen an ROI. 

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

We are customers and end-users. 

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

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Google
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Petronela Ghergulov - PeerSpot reviewer
Engineering Quality Analyst at Visteon Corporation
Real User
Top 5
Issue-free, straightforward to set up, and reliable
Pros and Cons
  • "The scalability is good."
  • "Perhaps the integration could be better."

What is our primary use case?

I primarily use it for verifying some things. We're using it as a repository. It's used for software code. 

What is most valuable?

I didn't have an option when coming to this solution. It was imposed on me. That said, I've had no problems so far. 

The solution is stable.

The scalability is good.

My understanding is that the setup is straightforward. 

What needs improvement?

I'm not sure of the complete capabilities of the tool as I don't use it that much. Perhaps the integration could be better. 

For how long have I used the solution?

I've used the solution for one year, however, not so regularly.

What do I think about the stability of the solution?

I have not heard of any stability complaints. My understanding is that the product is reliable. There are no bugs or glitches. It won't crash or freeze. 

What do I think about the scalability of the solution?

We have about 100 people using the solution in our organization. 

For our purposes, we find the solution scales well. It's okay. We've never had any issues. 

Which solution did I use previously and why did I switch?

We previously used IBM CLM and RTC.

How was the initial setup?

I did not directly handle the initial setup. There is an IT team, which is responsible for all the installation and setup tasks. I'm not sure how many people were involved in the deployment and maintenance of the solution. 

What about the implementation team?

Our IT team set the solution up.

What was our ROI?

I haven't looked into if we have noticed an ROI or not. 

What's my experience with pricing, setup cost, and licensing?

I can't speak to the exact cost or licensing structure. I don't deal with this aspect of the product. 

What other advice do I have?

I'd recommend the solution to others. I'd rate it eight out of ten. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Solution Architect at a tech services company with 11-50 employees
Real User
Easy to use, good integration with CIE, and good stability and scalability
Pros and Cons
  • "The most valuable features of Gitlab are integration with CIE and the ability to rapidly deploy solutions, projects, and applications. It is very easy to use, and there are no complaints."
  • "It could have more security integrations and the ability to check the vulnerability of the code. I don't think it is a responsibility of Gitlab, but it would be nice to have more options to integrate with."

What is our primary use case?

We are a consultancy company, and we mostly sell application tools such as Jira and Bitbucket, but sometimes, our clients have Gitlab or Github, and then we offer the consultancy experience in DevOps for improving the process.

All use cases for this solution are for the financial industry. Around 50% of our clients are financial services.

What is most valuable?

The most valuable features of Gitlab are integration with CIE and the ability to rapidly deploy solutions, projects, and applications. It is very easy to use, and there are no complaints.

What needs improvement?

It could have more security integrations and the ability to check the vulnerability of the code. I don't think it is a responsibility of Gitlab, but it would be nice to have more options to integrate with.

For how long have I used the solution?

I have been using this solution for about two or three years.

What do I think about the stability of the solution?

Its stability is good.

What do I think about the scalability of the solution?

Its scalability is good. Our clients are medium to large businesses.

How are customer service and technical support?

I have never used Gitlab's support.

Which solution did I use previously and why did I switch?

Sometimes, clients migrate from Gitlab to Bitbucket. Sometimes, they migrate from Bitbucket to Gitlab. The most important feature that they are looking for is more integration with other tools, and they find Bitbucket a better solution for that.

How was the initial setup?

It is straightforward.

What about the implementation team?

For deployment and maintenance, usually, most of our clients have one person who is a DevOps engineer or CCM Administrator. We contact them so that we can assist them.

Which other solutions did I evaluate?

The most evaluated option is Bitbucket. 

What other advice do I have?

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

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Reseller
PeerSpot user
Software System Team Leader at Ethiopian Roads Administration
Real User
Replicates with accuracy, scalable, and cost effective with premium options available

What is our primary use case?

During the development environment, we have a different number of developers, close to five. So each of them will have a different project. Maybe some of them do it in one project, but their assignment or the activity they are doing may be different, so they will do their activity and then they will push it to the GitLab. If there is an amendment or update required, they will pull it from GitLab and if they do their activity again, they will push it. 

What is most valuable?

GitLab also does the merging . The merging feature makes it easy later on for the deployment.

What needs improvement?

I would like to see security increased in the future. A secure environment is very important.

For how long have I used the solution?

I have been using GitLab for the past seven years.

What do I think about the stability of the solution?

The cloud provides good stability for GitLab.

What do I think about the scalability of the solution?

GitLab is scalable. I think they have their own actually premium services. So, there are some functionalities and features that may be added on top of the free version.

How was the initial setup?

The initial setup of GitLab is easy and straightforward. You do not need to be a deployment expert. It can be done by the managers or directors. 

What about the implementation team?

GitLab can be done in-house but we are using CloudWatch. All you need is to have a free account.

What's my experience with pricing, setup cost, and licensing?

The initial setup cost is excellent and you can add the premium features later.

What other advice do I have?

Using GitLab is important to help provide a more secure and reliable environment for developers working with information in the cloud. GitLab brings a level of safety. I would rate GitLab a ten out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user