Linked by Thom Holwerda on Wed 24th May 2017 20:02 UTC

Over the past 3 months, we have largely completed the rollout of Git/GVFS to the Windows team at Microsoft.

As a refresher, the Windows code base is approximately 3.5M files and, when checked in to a Git repo, results in a repo of about 300GB. Further, the Windows team is about 4,000 engineers and the engineering system produces 1,760 daily "lab builds" across 440 branches in addition to thousands of pull request validation builds. All 3 of the dimensions (file count, repo size and activity), independently, provide daunting scaling challenges and taken together they make it unbelievably challenging to create a great experience. Before the move to Git, in Source Depot, it was spread across 40+ depots and we had a tool to manage operations that spanned them.

As of my writing 3 months ago, we had all the code in one Git repo, a few hundred engineers using it and a small fraction (<10%) of the daily build load. Since then, we have rolled out in waves across the engineering team.

Thread beginning with comment 644734
To read all comments associated with this story, please click here.
Google has the largest single git repo
by nadiasvertex on Thu 25th May 2017 15:29 UTC
Member since:

The Google codebase includes approximately one billion files and has a history of approximately 35 million commits spanning Google's entire 18-year existence.

The repository contains 86TB of data, including approximately two billion lines of code in nine million unique source files.

Reply Score: 2

Lazarus Member since:

Not in one repository.

Reply Parent Score: 1

kokara4a Member since:

Not in one repository.

The linked article says otherwise. It's even in the URL.

Reply Parent Score: 2

Soulbender Member since:

That's not using Git though.

Reply Parent Score: 2