Add experimental CQ builder to test dual coverage

Bug: 1016925
Change-Id: I6e323826b49bff3fd98203417e2098df8d5f9cd6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2844390
Commit-Queue: Prakhar Asthana <pasthana@google.com>
Auto-Submit: Prakhar Asthana <pasthana@google.com>
Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874860}
GitOrigin-RevId: 00f52573af81eeb951522ba0bc239c1316ca8b1d
2 files changed
tree: 407bb71c71a4dbc20b6fa5372b71bf6b43bc5fdb
  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. README.md
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: