Likelihood to Recommend We started to use GitLab for hosting git source code repositories of our projects only but slowly we started to use it to store container images, packages, dependency proxy as well infrastucture registry and it is now well suited for Continuous Integration in our projects, It wasn't that good in Continuous Deployment before 12.0 version but after 12.0 it is amazingly good for Continuous Deployment as well since it keeps deployment information in a well organized manner which can be configure in ci yaml configuration.
Read full review Production ready, robust DB solution built for
Kubernetes envs, we was able, for the first time, to ship production db workloads inside k8s. Be sure to check differences with "traditional"
MySQL and other clustering solutions. Also be sure to match it with proper k8s storage solutions.
Read full review Pros GitLab excels in managing code versions, allowing easy tracking of changes, branch management, and merging contributions. It helps maintain code stability and reliability, saving time and effort in the development or research workflow. Powerful code review features, enabling collaboration and feedback among team members. Robust project management features, including issue tracking, kanban boards, and milestones. Read full review Easy and fast deployment. A reliable, fully automated, high-available db lifecycle management solution. Exaustive documentation. Production ready. Read full review Cons CI variables management is sometimes hard to use, for example, with File type variables. The scope of each variable is also hard to guess. Access Token: there are too many types (Personal, Project, global..), and it is hard to identify the scope and where it comes from once created. Runners: auto-scaled runners are for the moment hard to put in place, and monitoring is not easy. Read full review Some differences compared to "traditional" MySQL solution. Had some hard times trying to use it combined with pre-existing techs like WordPress, Magento, etc. The specific k8s environment features can have an impact on it, like the storage solutions offered by the cloud vendor. Read full review Likelihood to Renew Gitlab is the best in its segment. They have a free version, they have open-source software, they provide a good service with their SaaS product, they are a fully-remote company since the beginning (which means they are fully distributed and have forward-thinking IMO). I would certainly recommend them to everyone.
Read full review Usability I find it easy to use, I haven't had to do the integration work, so that's why it is a 9/10, cause I can't speak to how easy that part was or the initial set up, but day to day use is great!
Read full review Easy and fast deployment. A reliable, fully automated, high-available db lifecycle management solution. It requires a bit of learning time for people new to operators ecosystem.
Read full review Support Rating At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when
GitHub was acquired by Microsoft
Read full review Well documented, there was no need to contact support.
Read full review Alternatives Considered GitLab is easily the preferred tool when it comes to versioning and source control. With other tools the UI often feels outdated and clunky leading to inefficiency and confusion. With some of the sleeker tools such as
GitKraken , while the aesthetic is pleasing, the experience is plagued by a lack of support, lack of optional plugins, and a plethora of bugs that cause unnecessary legwork to resolve. GitLab is the best of both aesthetic and functionality
Read full review For a long time we struggled finding a viable solution to migrate our existing db workloads inside
Kubernetes . Before "operators era" proper db workloads required manual management, of course that easily raised administrative overhead. Then the future started to be brighter with the introduction of operators and the "official" Oracle's
MySQL Operator, then Presslab's one, finally Percona's operator. Compared to other operators, the last one allowed us to ship production db workloads inside k8s.
Read full review Return on Investment We were able to streamline our project's codebase which made us very organised and laid out a proper plan for development. Our deployment and infra pipelines are well structured now making our process 10x faster. We are more focused into project building rather infra, as infra is totally on autopilot mode. Which has enabled us to grow our ROI by records. Read full review It allowed us to use k8s on our entire infrastructure. Decreased administrative overhead around our db services. As it is an open source technology, it cut down our db pricings. Read full review ScreenShots