GitLab [Private Offer Only] Reviews

Our major use case for GitLab [Private Offer Only] is for development purposes, along with some resource sharing purposes. Because of that, the development is a full CI/CD workflow that is already implemented along with GitLab [Private Offer Only]. Our entire workflow development team is working on GitLab [Private Offer Only].

For our internal resource management, we are also doing some repository-side work. Internally, we are using GitLab [Private Offer Only] for internal resources. We have an on-GitLab [Private Offer Only] repository as well as a Wiki server for our documentation and other purposes, along with our CRM and ERP package. There is fully API-based integration between all these platforms.

The biggest advantage I see is the collaborative working with our development team because our development team has multiple domains, including a normal software development team, a telecom development team, and a hardware development team.

All of the development team work is there. For our R&D team, we are running a separate GitLab [Private Offer Only] repository for security reasons. From that repository to our production-level repository, we are managing separately for security reasons. That is the workflow we are using for the entire team.

We are using some AI-based code review mechanism in GitLab [Private Offer Only]. A code testing mechanism is also there. CI/CD is already there. We are also using an AI-based, Copilot-based code review mechanism. We now have code-level forensic inspection and credential sharing. That type of security side is also something we are in progress with; it is not completed. We are doing that type of work, especially on the security side of the already developed code.

On the ops side, the DevOps side, we are getting very good performance because of CI/CD integration in GitLab [Private Offer Only]. It is working very smoothly.

From the security side, we see that GitLab [Private Offer Only] is robust and satisfies our security concerns. In India, the government is initiating many regulations for the development side. My team has one department there. On the defense side, we are giving some projects. The government has instructed us to do many other testing purposes. We are also considering that. For some of our projects that are yet to roll out, development is almost completed. Testing is going on, quality testing is going on.

The reduction of our total consumption from the previous year regarding GitLab [Private Offer Only] shows a very drastic change because of this AI adoption on the development side. We reduced the four to five-month development time to four to five weeks, a maximum of one month. We are getting that much throughput with the same employee strength. We have not increased the employee strength, nor have we reduced the employee strength. From last year, with the same employee strength, we are getting five times higher throughput with the adoption of AI.

The built-in CI/CD integration in GitLab [Private Offer Only] is lacking. We are still depending on other packages. If GitLab [Private Offer Only] had some CI/CD integration internally, it would be beneficial. Because for CI/CD integration now, we are currently doing it with the direct server side. I think it is not that much integrated with the current scenarios of AI, that is AI agent-based or assistant-based coding patterns.

Some more improvement is required in GitLab [Private Offer Only] for CI/CD integration along with AI platforms. AI integration is basically what we need, especially on the CI/CD side of GitLab [Private Offer Only]. The code assistant, such as a cloud code assistant, is making things with GitLab [Private Offer Only], but it is conventional. They are pulling the code and sending the thing. I think they can do some more integration, seamless integration with GitLab [Private Offer Only]. AI is consuming GitLab [Private Offer Only] with the older style. If AI were fully pluggable in GitLab [Private Offer Only], it would be beneficial. I think we could get some more time reduction, especially on the testing side and the code testing side.

We have around four years of experience with GitLab [Private Offer Only].

I can tell around 90 percent stability for GitLab [Private Offer Only]. There is something in the 10 percent. I cannot say it is 100 percent. For this 10 percent with GitLab [Private Offer Only], it includes some glitches in the CI/CD integration; sometimes it is not working. We have seen some bugs, but in the later version, it was working fine. We are expecting some bugs now also. That is why I am making that 10 percent assessment. It is not excellent, but it is best.

Scalability in GitLab [Private Offer Only] is very much there. It is scalable. According to our requirements, it is meeting the scalability requirement.

We are mostly doing community support for GitLab [Private Offer Only]. We are not seeking direct support now. Community support from GitLab [Private Offer Only] is very good. We are happy with that. We are getting the solution very fast. For other platforms, such as Bitbucket and Azure DevOps, we have not gone fully with that. With GitLab [Private Offer Only] and other things, we are getting very good results.

Previously, we were using the free version of GitLab [Private Offer Only]. Now we are doing some projects with a paid version. Our mainstream is now in the free version. It has a bit higher pricing. Because of our employee count, our branches, and everything, we have multiple projects. There are many restrictions in the free version. I think GitLab [Private Offer Only] pricing is acceptable if there is a high-value project. Otherwise, for normal startups, they are still using the free version because of the price.

For a normal startup, at the starting time, GitLab [Private Offer Only] is very difficult to install. Now we have the skillset in our employees for managing and deploying GitLab [Private Offer Only] repositories. It has taken around four to five months for the experienced skillset to develop. The most difficult part of the deployment of GitLab [Private Offer Only] is the CI/CD integration for some multi-departmental project handling; it has taken a long time for that smooth CI/CD integration.

The return on investment for GitLab [Private Offer Only] for a higher value thing is very good. We get it very easily. We can get the ROI within one year itself. Nowadays, not one year, but five to six months, we will get the ROI.

For comparison with similar tools, we have mainly used GitLab [Private Offer Only] only.

For project management, we are only doing Agile with GitLab [Private Offer Only]. We have an in-house package to integrate with GitLab [Private Offer Only] for project management because we have different types of development domains, especially hardware, embedded, and AI software. In the software itself, there is a team and an ML team. We are managing all of these in a single project management suite. That project management suite is in-house developed based on the Agile platform.

GitLab [Private Offer Only] is on-premises because of the government projects. Previously, it was a hybrid.

We have not purchased anything from AWS Marketplace. We are mainly using Google Cloud and AWS. We are only depending on AWS for normal computing. For other packages and everything, we have an in-house team. We are mostly doing development in-house.

My overall review rating for GitLab [Private Offer Only] is a nine out of ten.

On-premises

Other

We use GitLab [Private Offer Only] as a source control and task management system for CI/CD. We have been using GitLab [Private Offer Only] for three years.

We utilize CI/CD, workflows, pipelines, and source repositories in GitLab [Private Offer Only]. The pipelines are built on these repositories, allowing for efficient workflow automation of over 15 projects.

All of our backlog and team tasks are included in GitLab [Private Offer Only] task management tool.

We are utilizing GitLab [Private Offer Only] APIs to capture data and have already built a dashboard to track team performance and project progress.

I would appreciate the benefits of the analytics features, but they are not available in our account or subscription plan. The pricing difference is too high for us to upgrade. We are currently utilizing 40 seats at approximately $29 per month in the premium subscription, while the ultimate plan costs $99 per month. The difference is too substantial for our budget.

We have been using this solution for three years.

We have not faced any issues with GitLab [Private Offer Only]. It has been stable throughout our use.

We purchased 40 seats, and sometimes we need about 10 more seats. Our seat requirements range from 40 to 50 seats per year.

I do not recall opening any tickets with GitLab [Private Offer Only]. We have not needed to contact customer service or support.

I previously used Azure DevOps and before that, we were using TFS, the older product from Azure. We sometimes use ClickUp as well.

We are using GitLab [Private Offer Only] as a cloud version in a SaaS deployment model.

Our implementation team consists of one administrator, a DevOps team of approximately two people, one project manager, and approximately eight additional administrators.

We are currently utilizing 40 seats at approximately $29 per month in the premium subscription.

Currently, 90% of our development activities are on GitLab [Private Offer Only].

We utilize some open source solutions to scan code before deployment. GitLab [Private Offer Only] is accessed directly from their website, and we are customers who purchased our seats directly from GitLab [Private Offer Only] website. I would rate this product overall at 8 out of 10.

Public Cloud

Other

My major use case for GitLab [Private Offer Only] is as a development repository for our own developed products. I started my experience with GitLab [Private Offer Only] about five years ago. The return on investment is not entirely clear; rather, we aim to achieve standardization by migrating everything to GitLab [Private Offer Only] so that it is fully standardized in terms of access controls.

GitLab [Private Offer Only] is completely isolated from the internet, which allows us to have our own private repository since there is no need to share the source code. This capability is one of the requirements for our company to have it on-premises. Additionally, I benefit from the Community Edition version, which is at zero cost.

The integrated code review feature in GitLab [Private Offer Only] helps with the development process because it is fully documented, including the process, the steps, the dates, and the persons who have approved the code changes.

I also benefit from the continuous integration feature in GitLab [Private Offer Only], which is part of our deployments.

The security protocols with GitLab [Private Offer Only] help with our security concerns, especially the on-premises capability and access with certificates and SSH keys, which work perfectly with no issues.

I think the free version of GitLab [Private Offer Only] is somewhat limited in integration with more advanced authentication, but we have not seen the need for that. I would not necessarily call this a disadvantage because it is a limitation purposely applied to the Community Edition version.

I would like to see more optimization in GitLab [Private Offer Only] as it places a high demand on computing resources. The application is quite heavy and requires a lot of CPU performance, which cannot be compared to cloud deployments that have more performance available.

Unexpected delays happen often, although it has never failed us. The response time is not very deterministic, and we did not have any database reliability issues. For scalability, I would not trust it in a very large environment, especially not the Community Edition version; for our eight developers, it is adequate.

I started using GitLab [Private Offer Only] about five years ago.

Unexpected delays happen often, although it has never failed us. The response time is not very deterministic, and we did not have any database reliability issues.

For scalability, I would not trust it in a very large environment, especially not the Community Edition version; for our eight developers, it is adequate.

I would rate GitLab [Private Offer Only] support an eight out of ten. The documentation of GitLab [Private Offer Only] is quite good, and with the use of AI, all of the questions are answered, so there is not really a problem.

We have used SVN in the past, an older type of version control system, and have now migrated most, almost all of our projects to GitLab [Private Offer Only].

It is fairly easy to install GitLab [Private Offer Only]. If you use Ubuntu, which is the recommended system, I set up another project in about thirty minutes, so it is very straightforward to do.

I am using only the free version of GitLab [Private Offer Only]. It is very affordable. The value for money with GitLab [Private Offer Only] is good, and that is certain.

I cannot really compare GitLab [Private Offer Only] with its competitors on the market such as GitHub; I can somewhat, but that information is outdated.

We are not using project management capabilities in GitLab [Private Offer Only] as we have another application for that, which is JIRA. With GitLab [Private Offer Only], I do not really see a reduction in our time to market, although the total overview and audit of changes is much better, allowing us to extract data from tickets and connect that information. However, I cannot say it really helps to improve time to market.

The room for improvement includes the limitations of the free version with integrations, room for improvement in authentication options, the application being heavy and requiring substantial computing resources, delays happening sometimes, and scalability could also be improved. I would rate this review an eight out of ten overall.

On-premises

Other

I am involved in automation testing. We have utilized GitLab [Private Offer Only]'s continuous integration feature because our automation code is in the CI/CD pipeline. We have implemented it via GitHub. I was involved in the user access setup during the initial setup. Once the user is given access throughout the project, it is about how much we have to automate our project.

This applies not just during setup, but during the actual project implementation.

The top feature that makes me use GitHub and GitLab [Private Offer Only] is that we can have CI/CD integrated. We can also maintain versions and get pull requests. These things are also very easy to implement, which is why we use it. GitLab [Private Offer Only]'s robust security protocols address my enterprise's security concerns because it is secure.

Using SSH, we are quite safe with how we share the access and everything. It is a safe and secure environment for an organization and teams to adopt it.

I have not explored that far with GitLab [Private Offer Only] because you mentioned project management. I have not used GitLab [Private Offer Only] or GitHub for project management.

I think if you can bring a holistic view in one place, that would be great. Because I have not explored it, I am not able to say what additional features you can bring in. I should know the full potential of the tool.

I have used GitHub for three years.

Regarding technical support, we had a couple of queries as part of multiple projects we worked on. They were on time, as per the SLA.

I used Jenkins earlier for CI/CD before GitLab [Private Offer Only]. Now we have come to this, partly because in certain cases, it is the client's preference.

In other cases, we also started using it organization-wide. Compared to previous tools, I would rate it an eight out of ten.

I would say the metrics to measure the impact of GitLab [Private Offer Only] on reducing time-to-market are the speed to deployment, how fast we can deploy, and how fast we can roll back to the previous stable version. These two are the metrics I would recall.

I do not go into the details of GitLab [Private Offer Only]'s pricing because my PM takes care of it as part of project procurement, billing, and all, so it is not in my hands. However, with the technical details of it, I could say it is quite comfortable to implement the CI/CD parts.

We did not use GitLab [Private Offer Only]'s project management capabilities.

I am quite comfortable with GitLab [Private Offer Only] as I do not think I am facing any major challenge because I use it in both interactive and non-interactive mode. In non-interactive mode, I can do larger things, so I am okay with it as of now.

We can integrate, and the interfaces are user-friendly in GitLab [Private Offer Only]. I feel it is good. GitLab [Private Offer Only] is widely prevalent, actually. Maybe marketing could help them reach even more. Their footprint could be larger, but in my opinion, they are already widely adopted.

I would rate my overall experience with this product an eight out of ten.