1886193 - Use more aggressive optimization strategies for new Android builds and tests

Status: RESOLVED FIXED

(Firefox Build System :: Task Configuration, task)

Description

[Andrew Halberstadt [:ahal]]

After the Android migration into Gecko, builds and tests are running on most autoland pushes. We need to set up the optimziations properly so they behave similarly to the existing Gecko builds and tests.

Off the top of my head, we'll need to:

1. Create a new "SCHEDULES" group based on the build application (firefox, fenix, focus-android).
2. Update SCHEDULES directives in moz.build for all files that exclusively impact one of those (e.g mobile/android/fenix -> fenix)
3. Update the task definitions with their associated SCHEDULES component
4. Update the task definitions to use the appropriate optimization (I think either the build or test aliases will apply here, though it's possible we'll need to make a new strategy).

Comment 1

[Andrew Halberstadt [:ahal]]

Attachment: Bug 1886193 - Use 'build' optimization strategy for new Android builds, r?#taskgraph-reviewers!

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/e9f5235da5b2
Use 'build' optimization strategy for new Android builds, r=geckoview-reviewers,taskgraph-reviewers,jcristau,tthibaud

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/17e43433790d
fix linting failures on conftest.py. r=fix CLOSED TREE

Comment 4

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/e9f5235da5b2
https://hg.mozilla.org/mozilla-central/rev/17e43433790d