Why Google Stores Billions of Lines of Code in a Single Repository (2016)

Re:Why Google Stores Billions of Lines of Code in a Single R... by m0zg on Sunday January 12, 2020 @06:14PM (#22030390)

You're doing it wrong: if _they_ want to change something that affects you, _they_ should be the ones doing the work to not break you. The situations where _you_ have to do anything more than a code review of such changes should be very rare. That's how it works at Google.

And besides, it's not like this gets any easier if you have multiple repos. Eventually you have to roll forward your dependencies, and doing the work that goes along with that.

[ Parent | on HN ]

Re:Why Google Stores Billions of Lines of Code in a Single R... by vanniv on Sunday January 12, 2020 @06:37PM (#22030541)

That's only how it works at Google if the "they" is sufficiently organizationally close that you actually care if you break them (and you'll only even know about it if you're close enough that you run their presubmit)

[ Parent | on HN ]

Re:Why Google Stores Billions of Lines of Code in a Single R... by m0zg on Monday January 13, 2020 @03:20AM (#22032751)

No, you don't have to "care". Presubmit _won't let you_ break them. That's the whole point of presubmit - to make sure tip of tree is green 100% of the time. You can't submit something that breaks the build _or_ breaks the tests. You can work with the code owner to make sure you can commit in the first place, but you don't get to just push your changes through and have the code owner deal with the fallout. Facepalm.

[ Parent | on HN ]