Case Study: Migration to GitLab (from Bitbucket) at AppsFlyer

1. Migrating To GitLab
How we moved from BitBucket to GitLab

2. ● Mobile Attribution & Analytics
● 14 offices worldwide
● All mobile platforms supported
● More than 35B events per day
● We are on 95% of the devices in the world!
● Cloud based (AWS,GCP)
● 680 Repos, 150 users
About AppsFlyer

3. So, we decided to
leave

4. We didn’t want to stay on a HOSTED
SOLUTION

5. BitBucket limitation
- API calls limit
- More latency

6. GitLab is Growing Fast
- Strong user base
- Fast releases
- Transparency

8. The Migration
Process

9. Key questions
Mercurial to Git - how to?
Architecture
Education
Tooling and integrations

10. Migrating to Git

11. Save history commits and tags
Fast, Simple, Safe

13. Basic Flow
Check if repo exists and last commit ->
Sync repo name & group ->
Convert it to Git ->
Push to GitLab ->
Notify to Slack

14. https://github.com/frej/fast-export

15. Team effort and self serve

16. Architecture

19. EFS

20. EFS

22. Monitoring

26. Lessons learned

27. - Restore saves old data-dir
- “file changed as we read it” while backup
- Unicorn workers increase

28. Education

29. Cover everything

30. Tooling and
integrations

32. add_to_slack.py

33. Sync validation

34. In-House Gitlab API

37. Easy to debug

38. Full technical post at:
http://bit.ly/af_gitlab

39. Thanks
elad.leev@appsflyer.com