GitLab Reviews

GitLab can be deployed on-premise and in the cloud and it is used for DevOps.

The most valuable feature of GitLab is its security.

The price of GitLab could improve, it is high.

I have been using GitLab for approximately one year.

The stability of GitLab is good.

GitLab is scalable.

The support from GitLab is good.

The price of GitLab could be better, it is expensive.

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

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.

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.

GitLab is a platform that facilitates hosting, collaboration and version control. We also make use of its pipeline capabilities. 

It is a speedy platform compared to the others I have used. I have also enjoyed using the platform as this solution offers a good user experience. 

We are currently using Atlasian Bitbucket, Jira and Confluence. Atlassian offers more products than GitLab. GitLab offers source control management, version control and collaboration between developers. Atlassian offers features on top of this as well as more integration points for developers.

I have used Gitlab for two months. 

This is a stable solution. 

This is a scalable solution. 

The configuration of Gitlab is straightforward. There is no site deployment of GitLab needed on behalf of the end user, especially if they are using the cloud version. 

GitLab's pricing is good compared to others on the market. 

If we compare the GitLab repositories to GitHub, GitHub has many issues since being acquired by Microsoft. GitLab is more independent and offers a better user experience compared to GitHub. Gitlab is easy to manage and is a good example of the Git-based collaboration tools.

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.

I am using GitLab for code management, such as code cloning, and code-to-data.

The most valuable feature of GitLab is its convenience. I am able to trace back most of my changes up to a far distance in time and it helps me to analyze and see the older version of the code.

The user interface could be more user-friendly. We do most of our operations through the website interface but it could be better.

I have been using GitLab for approximately three years.

I rate the stability of GitLab an eight out of ten.

I rate the scalability of GitLab an eight out of ten.

We have more than 1,000 developer users using this solution in my organization.

We have an internal administrator if we need help with the solution, I have not contacted GitLab for support.

I have used previously CVS. Both CVS and GitLab have their advantages and disadvantages. GitLab is in the cloud and can be accessed anywhere which is very flexible. For the functionality, I am not certain about the differences. I find them both to be good solutions.

I would recommend this solution to others that are doing code management.

I rate GitLab a seven out of ten.

I use GitLab to bring code from repositories.

GitLab's best feature is Actions.

GitLab would be improved with the addition of templates for deployment on local PCs.

I've been using GitLab since 2019.

GitLab is stable, I would rate its stability nine out of ten.

Previously we used Team Foundation Server, but GitLab is better for local cloud deployment.

The initial setup was simple.

GitLab is highly priced for smaller teams, but it's okay if considering a user base of thousands.

I would give GitLab a rating of nine out of ten.