GitLab Reviews

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.

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.

We are using GitLab for code management. We put code onto their servers. This allows developers to have a centralized place for code collaboration.

GitLab has helped our company save time. In our current project, we have split the job into two parts, one team is working on one particular feature and when done the solution merges the code together. Every two weeks we can release a new APK. We have the latest code in development so we don't need to merge code manually.

The solution receives frequent updates, it is always improving.

The most valuable feature of GitLab is the automatic merging of code.

I have been using GitLab for approximately seven years.

GitLab is highly stable.

The scalability of GitLab is good.

All developers are using GitLab in my company.

I plan to increase the usage of the solution in the future.

I rate the support from GitLab a four out of five.

Positive

I have previously used Bitbucket and Filezilla.

The initial setup of GitLab is easy.

There are different licensing options available, including a free limited-user license.

We evaluated other options before choosing GitLab.

One person can do the maintenance of the solution.

My advice to others is for them to use GitLab for managing their code.

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.

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. 

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

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

I have been using GitLab for the past seven years.

The cloud provides good stability for GitLab.

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.

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. 

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

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

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.

GitLab's best features are continuous integration and fast deployment.

GitLab's UI could be improved. In the next version, the documentation of the migrations steps should be better.

I've been working with GitLab for six years.

GitLab is very stable.

GitLab is scalable.

GitLab's technical support is quick and responsive.

Positive

The initial setup is pretty simple for GitLab as a service, but it's more complex for a hosted solution.

GitLab is comparatively expensive, but it provides value because it's feature-rich. I would rate its pricing four out of five.

I would rate GitLab nine out of ten.