To store the data.

Git merging allows us to track the details of how and who has done what. This is the best feature which is useful for all companies.

As we are using it in Kubernetes clusters, we don't have any issues.

GitLab needs to improve the CI/CD functionality because it is not compatible with Jenkins and other tools, as it is not that efficient. Security-wise, we have security features enabled in GitLab for code vulnerability and other aspects, but it is not up to market standards.

Approximately four to five years.

Recently we had an issue where an employee left the company and their commits were erased. We raised a request with GitLab support, but they were unable to help because they could not find the root cause of what went wrong. We restored the data from previous backups.

GitLab is suitable for small and mid-size organizations, but not for enterprise use.

We raised a request with GitLab support when an employee's commits were erased, but they were unable to help because they could not find the root cause of what went wrong.

Positive

I worked with GitLab Enterprise at a previous company. GitLab Enterprise is far better than the free version. For enterprise-level customers, we can recommend GitLab Enterprise. Regarding competitors, we have explored GitHub, Bitbucket, and CircleCI. However, GitLab Enterprise has more features than any of these tools.

I am working with Kyndryl, which is part of IBM. They have their own decision-making team who manages these aspects.

We are currently using general GitLab, not GitLab Premium.

We are using Jira and Confluence, but not Bitbucket.

We are currently using GitLab integrated with Sonar for code vulnerability checks, Jenkins, Camunda, and XL Deploy. We use Camunda to deploy folders and XL Deploy for server deployment.

We are not using the security features on the GitLab side, as we use different tools for that purpose. My team is not using the GitLab merge request process, but we work on providing GitLab access for admin activities, as developers are in different teams handling development and merge requests.

We are using basic features currently, so I cannot comment on detailed functionality comparisons. Every versioning control tool provides similar basic features, and we are not utilizing the full functionality of GitLab.

The system is easy to use.

On a scale of 1-10, this solution rates a 7.

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.

The solution's most valuable features are pipelines. GitLab allows you to automate things and show them diagrammatically.

The solution is much harder to get around and organize extra features. It has fewer options, and its UI is not so user-friendly.

I have been using GitLab for one year.

GitLab is a very stable solution.

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

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

Although the solution's documentation is publicly available, you have to invest much more time to read everything and understand how to get around.

On a scale from one to ten, where one is very easy and ten is difficult, I rate the solution's initial setup a six to seven out of ten.

The solution's pricing is acceptable.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a six out of ten.

I got familiar with the CI part of the tool. If you want to use all the features for testing and packaging, you have to use the paid version.

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

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 are using GitLab for team collaboration, code management, and certain CICD pipelines.

The most valuable features of GitLab are the CI/CD pipeline and code management.

Merge conflicts and repository maintenance could improve. If there is someone new to the system they would not know if there is a conflict.

In a feature release, it would be helpful if there was AI integrated into the system. For example, if there was a CI/CD pipeline available, we could configure them for our purpose without doing the process manually.

I have been using GitLab for approximately four years.

I rate the stability of GitLab a seven out of ten.

I rate the scalability setup of GitLab a seven out of ten.

I have experience using GitHub, but GitLab is a superior platform. One major advantage of GitLab is the ability to maintain a private cloud with a wide range of features. It also allows for quick setup of CI/CD pipelines. Garrett is becoming popular amongst developers for code maintenance.

The initial setup of GitLab takes a long time because there is a lot to configure.

I rate the initial setup of GitLab a seven out of ten.

I rate GitLab a seven out of ten.