My understanding of this is the Google approach is to have all builds in the cloud using Forge i.e. infrastructure that lets you cloud builds.
This means you can do hermetic builds, and thousands of other engineers can reuse the build artifacts you produce.
And in the particular context of tools such as code searching, your build artifacts update the code searching index pretty quickly post committing a change.
Re:Cloud Source Repositories
by toeenredbluo on Tuesday November 27, 2018 @03:59PM
(#18546650)
My point wasn't how do you build these things. It's how you index them.
How do you deal with compiler provided internals, where someone might be using clang which has behavior X, but gcc / icc / msvc doesn't?
These problems are more prominent in C/C++, but are everywhere... Not easy...
Google can probably check in everything for themselves... Probably not so easy for other companies? Maybe? Can Google solve this without sinking too much resources into it?