GitLab Reviews

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.

I am using GitLab primarily as a code repository and for CI/CD tools and deployments.

The feature I appreciate the most about GitLab is its ease of use and compatibility, which allows for straightforward building and deployment processes. 

Continuous integration with deployment is very powerful, which is a significant reason for migrating from TFS to GitLab. Its documentation is extensive, and YAML files are user-friendly, making the deployment process more or less straightforward.

There are missing search features, particularly when searching repositories or applying filters. Additionally, I have encountered issues with the deployment of CI/CD pipelines, especially dealing with variable environments. 

Creating a YAML file with numerous variables can be challenging without a way to separate them by different environments. It would be beneficial to have a user-friendly interface for setting up these configurations, instead of just writing YAML files.

I have been working with GitLab for a little over a year as I transition from TFS.

The stability of GitLab is impressive. Everything, including runners, functions smoothly without any issues.

Technical support from GitLab has been satisfactory. I have had meetings where they taught me, explained things, and provided guidance for starting from scratch. Overall, my experience has been pretty good.

Neutral

I am transitioning from TFS to GitLab, mainly due to the powerful continuous integration capabilities of GitLab.

Currently, I have two developers partially dedicated to creating the CI/CDs, Firebend, and repositories.

Migrating to GitLab is bringing time-saving benefits, and everything is easier to automate. This transition is crucial for us.

The pricing of GitLab is reasonable, aligning with what I consider to be average compared to competitors.

I am migrating from TFS to GitLab.

I would appreciate some AI-driven helpers, similar to Visual Studio's Copilot, integrated into GitLab. This could enhance the user experience by providing assistance during configuration. I rate GitLab a nine out of ten points.

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.

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.

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 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.

We use the solution as a source code manager or version control manager.

In our software development lifecycle, GitLab is used as a component for code repository management. We use GitLab for several projects to handle code repositories. For other software projects, we use Bitbucket, but the use case for both is very similar.

Many global users prefer GitLab for its enhanced pipeline automation for CI/CD features. It stands out among source code managers due to its parent-child pipeline feature. If users want to leverage this feature, they should consider using it. It’s not the only platform with this capability, but GitLab excels in automating many operations and offers integration with other platforms.

The solution supports platforms like Azure, GCP, and AWS. This capability makes it a preferred choice, even though other platforms also offer similar integration features. Additionally, GitLab’s tendency to be independent of ownership by another major company makes it an attractive option for many developers who prefer cloud usage

The tool's UI is good. 

In the next release, I would like to see GitLab expand its integration capabilities to include platforms like DigitalOcean, which developers widely use for cloud infrastructure. Enhancing CI/CD automation features specifically tailored for DigitalOcean would be beneficial. 

I have been working with the product for more than six months. 

The solution is stable. 

The product is scalable. 

The tool's technical support is great. 

The solution is free. 

I rate the overall product an eight out of ten. 

We create the pipeline and push it to GitLab to initiate the process. The cloud integration is straightforward.

When it comes to GitLab's CI/CD integration, it significantly supports our development process by accelerating deployments. With automated pipelines, we can focus more on development tasks without worrying about manual deployments, ultimately speeding up our development cycle.

In GitLab, I find the features and version control history to be most valuable for our development workflow. These aspects provide us with a clear view of changes and help us manage requests efficiently. I haven't utilized GitLab's security scanning capabilities yet. 

We plan to integrate tools like Sonicheap for code security. Currently, we use another product for security, focusing on Q4 security points.

We have used GitLab's features selectively for added security. We don't store passwords directly but use a secret manager and tools to sync passwords securely to our deployment environment.

I believe there's room for improvement in the advanced features, particularly in enhancing the pipeline functionalities. Better integration and usability within the pipeline could make a significant difference in user experience. I would suggest considering new features or functions that could streamline workflows further and make using GitLab even more efficient. Having additional functionalities that cater to specific needs could greatly enhance the overall experience with the platform.

I have been working with GitLab for the past 5 years. 

Regarding stability, while I can't rate it on a scale of one to ten, I can say that we've experienced good stability with GitLab, with no downtime or major issues.

I've had support from forums like Stack Overflow when needed. In my experience, GitLab integrates well with third-party tools like SonicWall and Slack without any major issues.

The setup process for GitLab is straightforward and easy to use.

Regarding pricing, I would rate GitLab as moderately priced, maybe around a seven or eight out of ten. It could be more flexible for clients but generally offers good value.

When comparing GitLab to competitors like Bitbucket, I find GitLab to be superior, especially in terms of features and functionality. Bitbucket still has its own strengths and is preferred by some organizations.

Overall, I would rate GitLab around eight or nine out of ten. I highly recommend it to other users for both company purposes and personal projects. GitLab provides a solid starting point for learning and working efficiently, making it a valuable tool for developers.