...
Chrome has always believed in the value of fast, remote builds for the Chromium project. We pioneered this by creating Goma, a remote build caching layer that has been available to Googlers, some Chromium project members, and as open source server and client libraries to all. As part of our next step in making faster builds more widely available and easier to deploy, Chrome is adding support for a new client build tool that uses the
Remote Execution API. The RE API is what underpins modern Goma today. With this change, we will simplify our usage of the API, and reduce the need for a separate standalone server.
Support for the new client build tool, which will be open source, will be added to the Chromium codebase over the next several quarters. While implementing direct support for the Remote Execution API within our build system will take some time, we wanted to provide an early heads-up to the Goma community that we are planning to move away from our usage of Goma codebase in the future. If you are dependent on the Goma Client or Server, you should be aware that after Chromium transitions to using Remote Execution directly, we intend to drop support for Goma in Chrome/Chromium build scripts and CI at a later date.
We are hopeful that transitioning our remote build support to a public standard will enable many more Chromium developers to be able take advantage of faster builds via any provider of the Remote Execution API, without the need to support bespoke infrastructure.
If you have questions or concerns, please reach out to
infr...@chromium.org.