![]() ![]()
GIT TAG MULTIPLE REPOSITORIES ANDROIDWe attempted to project CI utilization for our self-hosted mac mini runners, by looking at how many CI jobs are executed on the android mono repo.We extracted data from the CI jobs executed in the Android mono repo for the past 3 months, since post migration, we’d have a similar codebase and CI setup.With the multi repo setup on iOS, each project has it’s own customisable CI setup, including:įor moving to a mono repo, we needed data points around how many jobs would be executed in this new setup. GIT TAG MULTIPLE REPOSITORIES CODEHere, we evaluated the impact developers would have related to code ownership: Codebase setup vs Code Ownership points Projected CI utilisation This number doesn’t help us make a good call, because we’d be improving the experience for nearly half the devs, while deteriorating the experience for the other half. In Gojek, we have a split of 47% of devs working in Product teams and 53% working in Platform teams. Therefore, we can conclude that by moving to a mono repo, the devs in Platform teams would have an improved experience and the devs in Product teams would have a degraded experience compared to the existing multi repo setup. While developers in the Product teams can work on their product in a particular repository for up to weeks at a time and never have to touch another repository.īy moving to a mono repo: Impact of moving to a mono repo
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |