Ubuntu 22.04 for GitLab with maintenance support by ATH

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.

Public Cloud

Google

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.

My most common use cases for GitLab are development and managing repositories, primarily focused on code development work.

The features that are really useful for my use case generally include pulling, merging, and ensuring the pipeline is upright, which are very intuitive.

It helped me personally and my team to save time and money.

In terms of impact from using GitLab as an all-in-one DevOps platform, it helped with my project development life cycle.

Regarding improvements, making task management is something that GitLab can potentially make easier, similar to what DevOps or Jira does.

I have been working with GitLab for about two years.

The deployment and initial setup were not difficult for me to complete. The pipeline management was easy.

The setup process took less than an hour.

In terms of project management overall, I haven't faced any issues such as downtimes or losing the repository.

I haven't contacted technical support of GitLab.

When comparing GitLab with GitHub, I haven't really seen any noticeable difference.

I have worked with Azure DevOps before and found it really intuitive to use.

I have used GitHub and GitLab as well, and I find that they've been fairly intuitive to use.

Regarding GitLab, I purchased an enterprise license, though I'm not aware whether I or my company bought this license from AWS Marketplace or elsewhere.

I'm not aware of any integration with other tools or third-party applications.

I haven't faced any difficulties with user interface or deployment.

On a scale of 1-10, I rate GitLab an 8.

Private Cloud

Other

Our primary use case for GitLab  involves software development, such as storing sources, automation, and pipelines.

The features I find most useful for our development workflows include Git , merges, branches, code reviews, and pipelines. The code review tool is pretty good, and its general usability is commendable when compared to GitHub . It is user-friendly, easy to use, and easy to administer. GitLab  handles a significant amount of repositories, sources, and users effectively without data loss, even though it may slow down occasionally.

One significant feature we lack is the configuration that enforces code reviews, which simplifies the development life cycle. Unfortunately, this is available only at a higher license level than we currently use. Additionally, improvements are needed for stability, as the system tends to degrade over a few days and often requires a restart.

I have been working with GitLab for approximately six years.

The self-hosted version of GitLab is not very stable when under load. It slows down and requires restarts every few days. The updates are frequent and demanding, happening at least once a week due to security reasons. While understandable, this often breaks running pipelines.

In terms of scalability, GitLab in the cloud is easy to scale, but the self-hosted version is moderately easy, requiring some skills.

We have contacted support in a couple of situations, and they were responsive and okay.

Positive

We have used Subversion, GitHub , and GitLab.

The cloud-based setup is straightforward and easy. However, self-hosted setup is complex, requiring good DevOps and significant orchestration.

The pricing and cost are on par with other tools and are neither too expensive nor cheap.

I have evaluated Subversion, GitHub, and GitLab.

For those wanting to use GitLab, I recommend going with the cloud version as self-hosting is problematic. I rate GitLab an eight out of ten.

Private Cloud

Other

We use GitLab  for deploying our applications into different environments. It serves as more of a DevOps platform.

The CI/CD pipelines in GitLab  are highly valuable. Another important feature is the single source of repository, allowing efficient repository management and source code management. GitLab provides manageability by allowing us to manage source code effectively through separate repositories. Additionally, GitLab enables the creation of individual CI/CD pipelines for each repository, making software more agile. By integrating GitLab as a DevOps platform, we have enhanced agility, improved our time to market, and different teams can work collaboratively on various projects.

GitLab should embed security features when dealing with source code. It is essential to conduct proper testing, such as unit tests and code coverage, within the SDLC pipelines. Incorporating tools like JMeter  or load testing into the pipelines would be beneficial.

I have been working with GitLab for around four to five years.

The deployment process with GitLab takes approximately half an hour to forty-five minutes, which is not very time-consuming.

I have no complaints regarding stability. GitLab maintains an availability of 99% plus.

Currently, GitLab is not easy to scale because GitLab has specific deployment instructions. We deploy it on one of the VMs. For scaling, other deployment options from GitLab's side need to be adopted. Vertical scaling is different from horizontal scaling, and there are different types of scalability.

GitLab's support is very helpful. They utilize a severity and priority ticket system, with corresponding SLAs, to address our inquiries efficiently. The support team is quite knowledgeable.

Neutral

I previously used Jenkins . However, GitLab is a better tool because Jenkins  requires different plugins which need to be installed and managed individually, whereas GitLab is a more complete DevOps platform, requiring minimal integration.

GitLab is easy to set up, with guided instructions and documentation making the process straightforward. On a scale from one to ten, I would rate the ease of setup as eight.

Since adopting GitLab as a DevOps platform within the entire SDLC process, we have become more agile and improved our overall time to market.

GitLab is somewhat expensive. The cost depends on the subscription plan adopted, such as premium or ultimate, typically charged per user.

Jenkins is another tool I evaluated before choosing GitLab.

GitLab is a great tool that simplifies management and reliability. It allows the creation of individual CI/CD pipelines for different repositories, enhancing agility and helping software development teams expedite market delivery. I rate GitLab nine out of ten in overall satisfaction. My overall rating for GitLab is 9.

Public Cloud

Amazon Web Services  (AWS )