Project Hosting Alternatives and GitLab.com's Value Proposition

6 posts · Jan 2015 – Jul 2023

What this trail covers

GitLab.com has evolved as a robust, open-source, community-driven alternative to centralized project hosting services like GitHub and Bitbucket. This thread tracks its value proposition, emphasizing its free tier for unlimited repositories and collaborators, beautiful design, advanced contributor statistics, flexible repository grouping, powerful source code search, fine-grained permission management, integrated CI/CD, and seamless import capabilities. The platform aims to provide a superior and cost-effective solution for developers and organizations.

All GitLab trails

Jul 2023GitHub to GitLab migration the easy wayThis post details the process of migrating projects from GitHub to GitLab using GitLab's built-in importer. It covers the types of data that can be migrated (repository data, issues, pull requests, wiki pages, etc.) and the mapping of roles between GitHub and GitLab. It also provides a step-by-step guide on performing the import and manually migrating GitHub Actions to GitLab CI/CD by creating a `.gitlab-ci.yml` file. The post demonstrates the migration of a sample project, including its issues and merge requests, and shows how to translate GitHub Actions for linting, smoke tests, and unit tests into GitLab CI/CD jobs.
Oct 2022Arm Open Source makes a seamless migration to GitLabArm migrated ~200 open source projects from a mix of stand-alone Git servers and a public web-based Git service to GitLab's self-hosted platform. This migration was driven by the need to consolidate infrastructure, leverage Arm's own tooling due to GitLab's open-source nature, maintain control over proprietary code, and achieve cost savings. Arm collaborated with GitLab to ensure support for native Arm-based hardware. The migration also enabled fine-grained access control and redundancy via AWS Graviton EC2 instances. The process involved gradual deployment, security approvals, and has resulted in praise from engineering teams for ease of CI/CD setup, cost savings (15-20%), time savings on admin work, tool simplification, and improved collaboration.
Jan 2017CodePen, welcome to GitLab!This post details CodePen's migration to a self-managed GitLab instance, highlighting their motivations around control, security, and integrated CI/CD. It also covers their adoption of GitLab Issue Boards and Time Tracking for project management, replacing Trello. A key takeaway is the recommendation to use GitLab's importer tool for project migration.
Dec 2016Customer Story: Why Vaadin chose GitLabThis post details Vaadin's migration from a fragmented toolchain (Gitolite, Trac) to a self-managed GitLab instance. Key technical aspects include the use of GitLab Omnibus for easy installation and migration, integration with CAS for authentication, and the consolidation of 200 internal projects onto a single server with one configuration file. The post highlights the benefits of centralized project management, integrated issue tracking and code review, and improved developer workflow and collaboration.
Aug 2016Customer Story: Moving to GitLab! Yes, it's worth it!This post details a customer's migration from GitHub to GitLab, highlighting the cost-effectiveness of GitLab's self-hosted and cloud options compared to GitHub's pricing changes. It emphasizes GitLab's integrated CI/CD system (GitLab Runner) as a viable and cheaper alternative to third-party CI services like Travis-CI. The post also provides practical advice on installing and configuring GitLab CE, including common gotchas and Rails console usage for debugging.
Advertisement
May 2016The future of SaaS hosted Git repository pricingThis post discusses the evolution of SaaS Git repository pricing, highlighting GitHub's shift to unlimited private repositories and comparing it with GitLab's existing free offering of unlimited private repositories, unlimited contributors, and unlimited CI runners. It contrasts GitLab's per-user pricing model with GitHub's and Atlassian's approaches, emphasizing GitLab's commitment to making its solution accessible and comprehensive from idea to production. The post also touches on the business models of these platforms and explains why GitLab.com remains free.
Jan 2015The hardware that powers 100,000 git repositoriesThis post details the migration of GitLab.com from Amazon AWS to self-hosted hardware to manage costs and overcome scaling limitations. It describes the hardware configuration (HP DL180 G6 servers with dual X5690 processors, 32GB RAM, and 12x 2TB HDDs in RAID 10) used to host over 100,000 repositories. It also covers the implementation of DRBD for failover between two servers to ensure availability after moving away from AWS's managed services. The post concludes by noting plans to return to AWS for easier horizontal scaling and larger EBS volumes.