Why AppsFlyer moved from Bitbucket to GitLab

Research indicates a growing preference for GitLab as a version control system among developers, as evidenced by an increase in users choosing GitLab over GitHub and Bitbucket between 2018 and 2019. A significant challenge in transitioning to GitLab from other systems is the data migration process, which AppsFlyer successfully undertook by moving from Bitbucket to GitLab. AppsFlyer, a large engineering firm with over 300 developers, needed to switch due to issues like public repository access and latency problems with Bitbucket. They opted for GitLab due to its open-source nature, transparency, and better alignment with their growth needs. The transition required converting repositories from Mercurial to Git using tools like Fast-Export and developing a self-service wrapper for scalability. Additional benefits from the migration included improved repository management and developer trust. AppsFlyer also leveraged open-source capabilities by creating tools and API wrappers to streamline processes and increase codebase visibility. Despite some minor bugs post-migration, the switch to GitLab has been beneficial for AppsFlyer's growth and operational efficiency.

No tracked trend matches for this post yet.