Support depot_tools version pinning for release branches

Issue #2893 resolved
Marshall Greenblatt created an issue

The depot_tools checkout used for building Chromium is updated by default each time the script is run. This is problematic when building stable branches because the changes to depot_tools are not always backwards compatible (recent examples here, here and here). We should add the capability to pin known-good depot_tools versions (commit hashes) for stable branches to avoid unexpected breakages.

This can work as follows:

  1. Add a new depot_tools_checkout value to CHROMIUM_BUILD_COMPATIBILITY.txt to be specified when a release branch is created.
  2. Update to checkout that value, if specified.

We should continue to build master without depot_tools checkout pinning as an early warning system for breaking changes.

Comments (3)

  1. Log in to comment