GitLab Reviews

We used the solution for keeping Yama code files there for our project.

The solution could improve by providing more integration into the CI/CD pipeline, an autocomplete search tool, and more supporting documentation.

I have been using the solution for six months.

I have had no problem with the stability of the solution.

The solution is able to be scaled. We have been doing our own project and there has been no issue with scalability.

The installation can be difficult. You need to get used to the markdown files, the tutorials that are offered are not the best. I had to search the internet for alternatives tutorials. There should be clear instructions on how to create markdown files and how to upload code. There is a lot of room for improvement in the area of supporting documentation.

I would advise those wanting to implement this solution to create tutorials themselves because there are so many sources that you have to look at just to understand how to make a red blob or red marker onto the code.

I rate GitLab a seven out of ten.

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

It has improved the way our organization functions.

It is very easy to use.

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

It solves what the customers what.

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

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

We are always using the latest version.

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

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

We have used many solutions before GitLab.

The initial setup is straightforward.

The price is okay.

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.

My daily usage involves fetching code, creating branches, modifying the code, and then committing my changes. Once I'm ready for a review with my colleagues, I create a merge request. Then, during a code review, they will use the interface to write comments. Once everything in the comments has been addressed, I complete the merge. This describes a typical scenario.

We develop under Linux.

Everybody needs a source code versioning assistant, and GitLab is very flexible in this regard. 

GitLab offers a good interface for doing code reviews between two colleagues.

The continuous integration feature is good.

We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating. In general, integrating with third-party tools is easy for some but difficult for others. When I create a new project, I go through all of the settings, and then I can integrate that with other tools. However, with Jira, I have problems.

If we could have GitLab execute some of the system tests then it would be good because as it is now, we have to rely on another tool. Ideally, it would execute a system test, a unit test, and then create a report. It is possible to do it but requires a lot of scripting expertise. 

It should be easily available on their menu, similar to adding tests, configuring the tests you want to execute when you launch a build, so the build would be done then tests would be performed, and the report would be created.

This would allow us to know what went wrong during our systems test. If this aspect was more integrated into their interface, instead of relying on developers to script everything, it would be easier.

I would like to see better integration with third-party software.

I have been using GitLab for a bit more than a year.

GitLab is pretty stable. I would rate it an eight out of ten.

I haven't really used it outside of our Linux development environment, so I cannot really tell.

GitLab is not responding quickly enough to our request. I know one of the problems that I am experiencing is with the integration with Jira.

We submitted the request to GitLab and we did not receive any replies. That was back in October.

Technical support could be better and their response time needs improvement to respond more quickly.

Since I am using the web-based version and accessing GitLab through the web, I didn't have to install Gitlab, so in that sense, there was no effort, obstacles, or challenges in the initial setup.

I needed to understand the menu.

When I create a new software project in GitLab, I need to go through all of the settings to configure everything, which was not a problem. I needed to understand all of the options, and what it was doing.

I would rate this solution an eight out of ten.

We are using GitLab for managing our code. We have created branches and posted code, and as our team members complete assignments, the code is pushed to there.

The best thing is that as the developers work on separate tasks, all of the code goes there and the other team members don't have to wait on each other to finish. We can all work on our code in tandem.

The documentation could be improved to help newcomers better understand things like creating new branches. 

The company has been using GitLab for a year and a half, and I have been using it for between eight and nine months.

GitLab is a stable solution.

It is easy to scale with GitLab. We can do work on virtual machines, pushing the code there and working with it.

I have not had contact with technical support. Rather, I relied on the other developers for assistance.

We previously used BitBucket, but we have transferred everything to GitLab. Everything that BitBucket can do is available in GitLab.

In summary, this is a very good product and everything is working well. I would recommend it.

I would rate this solution a ten out of ten.

We are a startup company working on a new firewall product, and we use GitLab as part of the software development process.

I see this product as an investment. It speeds up our development, it's faster, safer, and more convenient. We know that all of your information is going to be in the same place and you can do what you want.

The most valuable feature of GitLab is the level of control that it offers. I have more control over everything.

I would like to see better integration with project management tools such as Jira. I know that integration does exist for some, but it can be better. In the future, I would like to be able to add what I want.

I have been using GitLab for one year.

This product is fully stable.

We have not used GitLab technical support because as of now, we haven't needed it yet.

Prior to using GitLab, I was using GitHub.

The initial setup is not complicated. Especially if you have used GitHub before, it is pretty easy. Being on the cloud, you don't have to buy a server or anything else. You pay for it, set it up, and all of the protection and other services are included.

GitLab can be used free of charge but if you use it for years and move to a paid license then it is better because you have more services. I think that we pay approximately $100 USD per month.

We strive to always have the latest technology. In this business, you have to follow your client and follow the trend. In fact, you have to do things ahead of the trend and be prepared. For us, this tool is really convenient.

My advice for anybody who is implementing this solution is to consider the paid version. Don't be afraid to pay a few dollars a year. Especially for a startup company, this tool is an investment. You don't have to look at it as an expenditure or expense. Don't think about it as spending money, but rather, investing money.

From my point of view and for what I use GitLab for, it is okay for me. There may be other products, but this is a great tool. It's convenient and it's used by a million developers. The developers here consider it to be the best choice. That said, there is always room for improvement in a product.

I would rate this solution a nine out of ten.

We primarily use this solution for repository tracking issues and reporting. We also use it for component integration. Our focus is pipeline field leads. We used to work with JIRA. I'm a developer and we are customers of GitLab. 

The solution is similar to all the repository tools or the work tools on the market. I like it and find it quite easy to use. 

The reporting could be improved and I'd like to see some testing or other deployment tools and integration with third parties. 

I've been using this solution for five years. 

This is a stable solution. 

This is a scalable solution. 

The initial setup is straightforward. 

Depending on the situation, I would recommend it. 

I would rate this solution an eight out of 10. 

Overall, our team is happy with the solution.

The CI/CD pipeline management is the solution's most valuable aspect.

Everything is easy to configure and easy to work with. Our team finds it to be very user-friendly.

Generally, the volume control is very good.

I've looked at GitLab's roadmap. The only thing our company is really waiting on in terms of features is the development of metrics. We're looking forward to being able to take advantage of them.

We've been using the solution for two years at this point.

We've never had any issues with stability. We're very happy with the setup we have and it works well for our team. We haven't had any issues with the product crashing or freezing and I don't recall dealing with bugs or glitches.

The solution is very scalable. I'm not sure how many nodes we have currently, however, it is scalable. If we need the extra capacity, I know we can build it out and use different setups.

We have about 100 users in our company using the product.

We've never needed to contact GitLab for technical support. I can't speak to the level of service their in-house team might give.

We previously used SVN. We migrated everything over to GitLab.

Our platform engineering team found the initial implementation pretty straightforward.

Within the organization, deployment took about a week. That said, we had to spend three weeks migrating from SVN, which is what we were using before.

There isn't really any maintenance required. It's not something we think about or worry about, really.

We're just a customer. We don't have a professional relationship with GitLab.

We're using the latest version of the solution right now.

I would definitely recommend the solution to other organizations. It's pretty easy to use and can scale if you need to. It's stable as well. We're not really missing any features. It's great.

Overall, I'd rate GitLab nine out of ten. They can always improve, which is why I didn't give them a perfect score. What they are working on, based on their roadmap, is already quite impressive. We're looking forward to metrics coming down the pipeline later in the year.

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.