Migrating from BitBucket to
summary
AppsFlyer moves from Bitbucket/Mercurial to GitLab, converting repos with fast-export and running a self-serve one-liner migration tool that checks GitLab, locks the Bitbucket repo, converts and pushes, and notifies teams via Slack. Architecture runs two GitLab instances behind a console, PostgreSQL, Redis, managed Elasticsearch, and NFS after EFS fails on many tiny Git files; daily restores to GCP prove backups work. Built an internal GitLab API wrapper, found many dead repos, and fixed backup race and disk-rotation bugs.
AI-written summary · about
chapters (12)
- 0:00Introduction and context
- 0:57Company overview and scale
- 2:02Migration motivation
- 4:25Choosing GitLab
- 5:27Migration planning
- 6:22Migration process and tools
- 8:49Migration benefits and tips
- 9:53Developer education
- 11:06GitLab architecture
- 12:55Backup and disaster recovery
- 13:49Automation and API wrapper
- 17:14Post-migration retrospective
related talks
24mA One Woman Show of Migrating an Entire R&D SCM From Bitbucket Cloud to a Self-Hosted GitLab
38mHow We Scaled GitLab For a 30k-employee Company
22mHow We Migrated Thousands of Repositories to SaaS With Developer Experience
27mB How GitLab scaled Git access with Go and what we gained from it
21mFighting Git Workflows
27mDo the magic with DevOps, Open Source and All-remote teams (with Python, of course)
22mThe place of GitLab within a mobile team's processes
46mFrom 1,000 to 5,000 Users: Scaling GitLab Without (Too Much) Pain