e7c4f90651
For now I think I have to run mb + ninja on testers in order to generate the proto used by webrtc_dashboard_upload.py. I would prefer a solution where we build on the builder and distribute via isolate, but let's do this for now (it will have to be the solution if isolate doesn't work out). Also remove obsolete entries. I think the previous code used to try to list all bots, but it clearly failed at that. The error one gets when an unlisted bot runs mb is very clear anyway. Bug: chromium:1029452 Change-Id: I2f4dda24ef0fb0337439c30c065b29b0da6bbe16 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/168527 Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Patrik Höglund <phoglund@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30521}
MB - The Meta-Build wrapper
MB is a simple wrapper intended 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 is meant to use GN or GYP.
It supports two main functions:
-
"gen" - the main
gyp_chromium/gn geninvocation that generates the Ninja files needed for the build. -
"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: