GitLab Reviews

We have a normal use case to build source code and our agenda and then try to deploy it. The deployment is not specifically automated, it is semi-automated. So it is normal. We create an artifact, try to build it, and then deploy it onto the application server. It's not fully automated. 

At this point, I think the features are declining. 

We like that we can create branches and then the branches can be reviewed and you can mesh those branches back. You can independently work with your own branch, you don't need to really control the core of other people. 

There could be more features in GitLab, but we are as of now not using the full-fledged feature set. 

Another good feature is the code review, which also helps us with peer review. It helps in giving part of the code and giving back whatever the branch that the developer is working on. It can then be merged once it is thoroughly reviewed. Those are certain things that I think are helpful from a developer's point of view. It provides or mandates quantitative code into the master.

We do reviews as I also work with some of the leadership teams. Leadership teams generally focus on statistics, metrics, or some sort of dashboard. They would like to have the ability to categorize these things. They would like to have a very high-level view. That would help. Someone who is not really a developer, but a leadership team. They are always interested in statistics or metrics features. That is something I would see imbedded into GitLab. That would help someone who is from the outside take a view and understand how qualitative the code is, because they cannot definitely dive in and look at the code, and they will not be able to understand all the details. At a high level, if they want to see and understand, at least they will have some confidence about how the projects are going on.

I have been using GitLab for two years. 

The stability is good. I never had any issues. Stability-wise, I'm comfortable with it. 

Scalability-wise it is very scalable as well. Based on the code volume, there is a scope for improvement. I never had issues with scalability.

Technical support depends on licensing. We haven't reached out that frequently because it is stable and we don't see any issues. I don't recall anything that we had any particular challenge that we had to reach out immediately to GitLab and then get the answer quicker at any point in time.

I wasn't here for the deployment but the deployment takes around 10 minutes. 

Only a few aspects will take close to five minutes. 

I would rate GitLab an eight out of ten. 

GitLab provides some sort of static analysis part. That is what I understand, but I never tried it. I would like to see static analysis also embedded in GitLab. That would also help us. If there's something that it does internally by GitLab and then that is already tied up with your pipeline and then it can tell you that you're coding is good or your code is not great. Based on that, it would pass or fail. That should be streamlined. I would think that would help to a greater extent, in terms of having one solution rather than depending on multiple vendors.

The primary use of the solution is for LCDs and as a repository.

In GitLab, the most valuable feature is using information with a repository and using a containerized approach. You can use containers to create different jobs. 

The dashboard and interface make it easy to use.

GitLab doesn't have AWS integration. It would be better to have integration with other container management environments beyond Kubernetes. It has very good integration with Kubernetes, but it doesn't have good integration with, for example, AWS, ETS, etc.

The solution is stable. So far, we have not experienced any problems or bugs.

Coming from container architecture makes it very scalable. Every job you create will be created with its own container so it doesn't create laws on the existing running jobs on other containers. It expands itself by usage.

As the solution is open-source, there isn't any particular support subscription. There's a community, which is usually quite fast but it's not dedicated to any particular company. It's not certain that you will get the support you need by a certain time. You have to figure it out by yourself. It's quite easy to do so, however. If you have people on your team who have knowledge about containerized technologies, then it's actually not a problem.

We previously used Jenkins. Jenkins management is more complicated than GitLab. GitLab is easier to manage. Because of the simplicity of the product, GitLab is better than Jenkins.

The solution was very straightforward to implement.

Another team did the implementation, but if you use public cloud software, you don't need to deploy anything.

The solution is open-source.

We use the public cloud deployment model.

I would rate the solution 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.

My primary use case is for creating pipelines and automation workflows.

By streamlining tasks that we used to do on a daily basis and scheduling them.

CI/CD, GitLab scanning, and the cloud are the most valuable features. 

There is room for improvement in GitLab Agents. 

I would like to see more features focused on GitLab or CICD. I am not sure if  there is a roadmap for GitLab CI/CD Elite.

I have been using GitLab for five years. I am currently using version 14.5.

It is a stable solution. I would rate it an eight out of ten. 

I would rate the scalability of GitLab a three out of ten. It is low. 

It can be challenging to scale. Sharing databases and removing multiple VPNs is not easy to handle. GitLab's stability is not as good as other platforms that offer Kubernetes engines. We use OEMs instead.

There are 300 to 400 users in my company. We definitely plan to increase the usage. 

We are familiar with GitHub. 

I'll give the initial setup a six, slightly above average, where one is difficult and ten is easy.

Now we automate everything, so let's say the deployment now takes about one hour to deploy.

For the deployment process, we create a template and prepare the VM on our cloud. Then we deploy the container using the controller, which deploys the solution.

We had IT specialists and engineers for the deployment process. 

It's a bit tricky because we have a different license. I rate the pricing mode a five out of ten for now, but it might change in the future. We have an educational license, and support is not included.

GitLab offers various services, and it's important to understand which ones you truly need. Service providers might have different capabilities, and compatibility with your existing devices can be a critical issue. We haven't faced many problems with network compatibility or duplicated services so far. 

If I could go back in time, I would recommend using GitLab primarily as a reliable repository. For additional features like scanning and monitoring, it might be beneficial to explore other specialized solutions.

Overall, I would rate the solution an eight out of ten. 

We are using GitLab for team collaboration, code management, and certain CICD pipelines.

The most valuable features of GitLab are the CI/CD pipeline and code management.

Merge conflicts and repository maintenance could improve. If there is someone new to the system they would not know if there is a conflict.

In a feature release, it would be helpful if there was AI integrated into the system. For example, if there was a CI/CD pipeline available, we could configure them for our purpose without doing the process manually.

I have been using GitLab for approximately four years.

I rate the stability of GitLab a seven out of ten.

I rate the scalability setup of GitLab a seven out of ten.

I have experience using GitHub, but GitLab is a superior platform. One major advantage of GitLab is the ability to maintain a private cloud with a wide range of features. It also allows for quick setup of CI/CD pipelines. Garrett is becoming popular amongst developers for code maintenance.

The initial setup of GitLab takes a long time because there is a lot to configure.

I rate the initial setup of GitLab a seven out of ten.

I rate GitLab a 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.

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.