[infra]Create experimental builder for the ml rts experiment

Bug: 1289329
Change-Id: I0712d3d80bff4cf1cd7394689a4780bd8ff6bc6c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3654502
Reviewed-by: Garrett Beaty <gbeaty@google.com>
Commit-Queue: Struan Shrimpton <sshrimp@google.com>
Cr-Commit-Position: refs/heads/main@{#1006625}
NOKEYCHECK=True
GitOrigin-RevId: fd07359ad1a52631a656c37a6674b6cc70f66855
2 files changed
tree: 439306e8563cd939e8a008e0d9ccee42f75843ac
  1. docs/
  2. lib/
  3. mb_config_expectations/
  4. __init__.py
  5. DIR_METADATA
  6. mb
  7. mb.bat
  8. mb.py
  9. mb_config.pyl
  10. mb_unittest.py
  11. mb_validation_unittest.py
  12. OWNERS
  13. PRESUBMIT.py
  14. PRESUBMIT_test.py
  15. README.md
  16. rts_banned_suites.json
README.md

MB - The Meta-Build wrapper

MB is a simple wrapper around the GN build tool.

It was originally written as part of the GYP->GN migration, in order to provide a uniform interface to either GYP or GN, such that users and bots can call one script and not need to worry about whether a given bot was meant to use GN or GYP.

It eventually grew additional functionality and is now still used even though everything is GN-only.

It supports two main functions:

  1. “gen” - the main gn gen invocation that generates the Ninja files needed for the build.

  2. “analyze” - the step that takes a list of modified files and a list of desired targets and reports which targets will need to be rebuilt.

We also use MB as a forcing function to collect all of the different build configurations that we actually support for Chromium builds into one place, in //tools/mb/mb_config.pyl.

For more information, see: