GitLab Reviews

Mainly, we use GitLab as a source control repository, and I use GitLab CI for the CI/CD pipeline.

GitLab's source control is excellent. Having the source control and pipeline in the same platform makes integration seamless. It is already integrated, with no need to configure any webhooks or other settings. 

Implementing CI/CD with GitLab has accelerated the time to market significantly. As we implement automated testing and DevSecOps, it speeds up the process by forty to sixty percent.

GitLab should enhance its GitOps capability as they are currently using FluxCD, however, Argo CD is better and offers more features. GitLab should work on improving their user interface for GitOps as it is lagging behind.

I have been working with GitLab for more than three years now.

GitLab is very stable with no issues in performance or availability.

GitLab is highly scalable, but in our current architecture using Docker containers, it isn't. That is why we're transitioning to OpenShift for future scalability with increased user numbers.

I have interacted with architects for some advice during the implementation, and they were prompt in their response. However, I have not had to open any support tickets yet.

I have worked with several CI/CD tools, including Jenkins, Azure DevOps, Tekton, and Jenkins. GitLab CI is more powerful than Jenkins and Azure DevOps and comparable to Tekton.

The initial setup of GitLab was straightforward. We have it installed as a Linux package and as a Docker container, which took very little time.

I have used Tekton before, the vanilla version on Kubernetes and Red Hat's version of the pipeline.

Overall, I recommend GitLab to other DevOps teams due to its powerful CI capabilities and having most tools you need on the same platform. It enables seamless integration and automation. I rate GitLab nine out of ten.

We are using GitLab for source code configuration and for CI/CD processes.

The CI/CD process is very efficient. We are utilizing the pipelines extensively and gaining significant benefits from GitLab.

We are not using the AI process yet, however, I would like to see AI support in GitLab. Maybe it already does. I am not sure how it supports AI processes.

We have been using GitLab for two years.

GitLab supports us very well.

We do not have any direct technical support from GitLab. We ask questions to our IT department, and they may seek external support if needed.

Neutral

We have just tried Jenkins. We are using GitLab. GitLab has better support, and its features are superior compared to Jenkins.

The initial setup was handled by our IT department.

GitLab is a cost-saving tool and is particularly effective for coding processes.

I do not have any recommendations or suggestions. I rate GitLab a ten out of ten.

We were using GitLab as a repository for our project. Whenever we were developing anything, we would commit our codes there. 

We used it for creating branches, merging branches, and comparing branches to resolve conflicts during code committing. We configured the CI/CD pipeline to automate our deployment process. We also utilized it in conjunction with tools like Octopus and OpenShift.

GitLab helped us streamline our code-committing and versioning process. It provided better user-friendly solutions for comparing and resolving conflicts when committing code. 

The CI/CD pipeline setup was straightforward and required fewer commands, making it simpler to use compared to Tekton. This efficiency in code management and deployment contributed to smoother operations in our projects.

The most valuable aspects of GitLab are the ability to create branches, merge branches, and compare branches to resolve code conflicts. 

The documentation provided by GitLab is very comprehensive, which is useful for resolving queries. GitLab's logs are also beneficial for tracking the status of our CI/CD pipeline.

GitLab can improve its user interface to make conflict resolution more user-friendly. Better and more descriptive logs during CI/CD pipeline configuration would also be beneficial to diagnose issues more quickly. 

Sometimes, the logs provided are not sufficient to understand the errors, and we needed assistance from our DevOps team.

I have been using GitLab for around four to five years.

I have not experienced any performance or stability issues with GitLab so far.

GitLab is scalable and works well with multiple environments. It integrates well with other tools. It has all the features required for our coding and deployment needs, which makes it scalable to our changing requirements.

I did not have the opportunity to engage with GitLab's technical support as I did not encounter any issues requiring escalation.

Neutral

The initial setup was straightforward. There were no challenges beyond typical configuration, and the documentation was adequate.

Our DevOps team handled most of the configuration work, and we, as developers, made changes only occasionally for personal use scenarios.

I have never paid for using GitLab personally, as it is free for our usage purposes. Even when working in other small organizations, we opted for GitLab as it was cost-efficient.

I would recommend GitLab to others because it is free and user-friendly. It provides all the necessary functionalities we need.

I'd rate the solution seven out of ten.

I use GitLab to manage our development lifecycle. We use it to store code and automate our CI/CD pipeline. Once developers commit their code, the CI/CD pipeline automatically starts, supporting development through various stages. It is part of our software development life cycle.

GitLab enhances productivity and reduces time since many tasks are automated. I appreciate the team collaboration it offers, enabling multiple people to work on the same Git repository seamlessly. 

Additionally, it streamlines our DevOps processes with automated CI/CD pipelines.

There are some challenges with repository file management as GitLab may struggle to manage larger files. Improvements could be made regarding size management and file partitioning. 

Also, the UI has remained the same for a couple of years and could benefit from an update with AI features and better customization.

I have been using GitLab for three or four years.

I have not encountered any performance or stability issues with GitLab so far. It has remained stable and reliable.

GitLab is scalable as multiple users can simultaneously access it without issues.

We have rarely needed to escalate issues to technical support since GitLab usually runs seamlessly. Occasionally, issues might arise if the URL isn't up or due to server problems.

Positive

I have worked with Bitbucket. In comparison, GitLab is more advanced, particularly in terms of cloud capabilities.

Setting up GitLab is smooth and straightforward. There is no complexity as long as you're familiar with the basics. A simple code can be reused, facilitating easy installation and use.

GitLab is mostly free, with potential costs arising from upgrade versions. There is a trial period of about six months during which it is free. Afterward, fees apply.

I have experience with Bitbucket and Jenkins, and both serve as alternatives to GitLab for version control and CI/CD pipelines.

I recommend GitLab for DevOps engineers. It is easy and fast to use. While Jenkins is also good for understanding, GitLab offers an easier user experience. I rate GitLab as ten on a scale of one to ten.

When a developer checks in code, it is automatically built and deployed, and automated test cases are also run. We have extensive integration with GitLab, which helps us with source code management. We run the static code analysis using SonarQube. 

Technologies are always changing. Nowadays, new things like serverless computing and workload management have emerged. We have noticed a few gap items for faster service delivery. For example, we do user interface testing in the latest team and automate it using some tools. Recently, we integrated a tool with user interface testing, which can simulate a multi-user environment. So, we would like to see more integration with different platforms.

We normally do load testing for an hour, extending that load with two or three different use cases. We increase the load by two or three times to check how the application responds. This helps us see if the application can withstand increased load, though it may reject messages or requests when it can't handle two to three times the normal load.

We do endurance or soak testing by leaving the system at the rated load, like 300 requests per second, for 12-16 hours to observe stability. We monitor for CPU leakage, memory leakage, queue building, and similar issues. If there are any problems, we fine-tune and fix them. For performance testing, we test at multiple levels: one at the service level and two at the system level. We normally don't test at the integration level.

My company has 90 users. 

The solution's deployment is straightforward. We have containerized applications that are deployed to the environment. 

GitLab was deployed in-house. 

The main value and impact of using the product are significant. We create and maintain vulnerability-free software by integrating tools like ManageEngine, which periodically patches our runtime environments, including operating systems, kernels, and software. Additionally, we run automated Nessus scans periodically, every week and day, to identify new vulnerabilities even after applying patches.

I rate the overall solution an eight out of ten. 

We do two levels of security scanning. One is at the build level, where we integrate with security packages and use tools like OWASP for top vulnerability compliance. This ensures that all third-party tools, like Tomcat and JBoss, are scanned as part of the build.

The second level is a reactive scan at runtime. We scan Oracle clients, JDKs, JBoss, Tomcat, Log4j, and other components during runtime. We also consider the operating system's security. Before we complete software testing, we use Nessus to perform a runtime security scan.

We are not using the community version of GitLab, but we are using it for ticketing and publishing the tool versioning.

The best features of GitLab are versioning and keeping track of the versions.

GitLab helps me save time and provide financial benefits, as keeping track of the updated version and the changes is money and time-saving.

GitLab has CI/CD pipeline capabilities.

I have been working with GitLab for probably six to seven years.

I am satisfied with GitLab's security, and we have not experienced any problems so far.

Regarding scalability, I did not face any issues with GitLab supporting my projects.

I have not contacted GitLab's technical support.

Neutral

I have seen benefits from using GitLab, since my directors and the team are using it, they must be happy with it.

I rate GitLab seven out of ten because nothing is perfect. I think we have to finish the conversation. I have told you what I could tell you.

We primarily use GitLab for code migration and version management. It helps us maintain metadata, manage versions, and facilitate continuous integration when working in teams. When working on a feature, we create a feature branch, which allows us to work on the feature independently. Once the feature is complete, it must be merged into the main branch. This streamlines the process of deploying the application to the production environment.

We use some orchestration tools to do it. We have our own built packet manager, and that package manager interacts with the excellent migration and everything internally.

The important feature is the entire process of versioning source code maintenance and easy deployment. It is a necessity for the CI/CD pipeline.

There is a need to improve or adopt AI into the ecosystem like a co-pilot, which Microsoft has done with GitHub.

I have been using GitLab for nine years. I have worked across version management for continuous integration and deployment.

The product sometimes crashes.

I rate the solution’s stability a seven out of ten.

The solution’s scalability is good.

I rate the solution’s scalability an eight out of ten.

I have used GitHub before. GitHub now comes with an AI Assistant, similar to a copilot, its most significant advantage. With this copilot, it assists you in writing code. It provides examples and helps you rectify errors, especially during migration processes. Additionally, it offers previews of how migration can be performed. These enhancements are attributed to Microsoft’s support and involvement in OpenAI.

The initial setup is easy and depends on the target enrollment; it typically takes just a few minutes to complete. Migration is also handled efficiently, typically in less than a few minutes or between three to five minutes, depending on the data size you want to migrate. The only drawback or consequence is that you need a private Git repository, which GitLab should provide by default.

For small-scale usage, GitLab offers a free tier. For enterprise pricing, GitLab is more expensive than GitHub, as it's not as widely adopted. GitLab is the preferred choice for many developers despite its higher monthly pricing plan, which is around $126.

GitLab has improved our CI/CD processes in software dependency management. It handles conflicts between versions seamlessly, such as when merging different features into the main branch. With GitLab, there are no conflicts in the code itself. Versioning is also efficiently managed within GitLab, allowing us to easily track the latest main branches, previous branches, and releases. For example, if a software depends on specific versions, it's easily traceable using GitLab. One of the most significant advantages is the built-in DTS, which supports ample file storage. This capability allows us to store 30-40 gigabytes of repository sizes.

The code diffs available in GitLab show the differences between the older version and the current one, indicating what has been added, deleted, or modified across the codebase. This helps you understand which portions of the code have changed within a particular file, such as a Python script, aiding in traceability and version management.

The merge request feature is standard and available even in GitHub, making it accessible on most Git platforms. It is one of the fundamental features of GitLab, a free product.

Overall, I rate the solution a seven out of ten.

GitLab is predominantly used for software development and practicing DevOps. GitLab CI/CD is one of the best features, and the solution is used primarily for software development.

GitLab is robust software and easy to use. There is excellent documentation available on their site but it can be overwhelming for early learners. 

They incorporate new features every September, and they have introduced their own code editor and AI features.

The pricing has been substantially increased, which is a major concern. While GitLab has a lot of documentation, the complexity and volume can be overwhelming, especially for new learners. Structuring the documentation more effectively could help alleviate this issue.

GitLab was resold for approximately two years.

The solution is stable, and there have been no noted glitches or latency issues.

The solution is easy to scale.

Customer service and support are good.

Positive

Previously we worked as resellers of other IT software like Snyk and Aqua Cloud Security.

The initial setup is medium in terms of difficulty. It's neither too easy nor too difficult.

Pricing is relatively expensive.

Previously explored solutions like Snyk and Aqua Cloud Security.

GitLab is a very good solution.

I'd rate the solution nine out of ten.