mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-12-12 09:01:16 +00:00
7176a9a02c
By setting these to the "build" optimization, it means that bugbug will apply its machine learning algorithm on autoland and with `mach try auto`. But in addition, this also sets up some new SCHEDULES rules. A new mutually exclusive SCHEDULES group around the "application" is created. Namely it can be one of: - firefox - fenix - focus-android Files under `/browser` are tagged with the "firefox" component, while files under `mobile/android` will be tagged with both "fenix" and "focus-android" components. Files under the `mobile/android/fenix` or `mobile/android/focus-android` dirs are further restricted to their respective component. Note that any files that can impact Gecko should not be tagged with any of these components. On the task side, all of the prior Firefox builds and tests are tagged with the "firefox" component, while all of the new Android builds and tests are tagged with "fenix", "focus-android" or both (depending on the task). The upshot of all this, is that patches that *only* modify files under `/mobile/android` will not run any of the Firefox builds and tests. Conversely patches that *only* modify files under `/browser` will not run any of the Android builds and tests. Differential Revision: https://phabricator.services.mozilla.com/D205127 |
||
|---|---|---|
| .. | ||
| android_taskgraph | ||
| ci | ||
| docker | ||
| docs | ||
| gecko_taskgraph | ||
| scripts | ||
| test | ||
| .yamllint | ||
| mach_commands.py | ||
| moz.build | ||