Closed Bug 1405376 (gradle-automation-v1) Opened 3 years ago Closed 3 years ago

[meta] Use Gradle to build Firefox for Android in automation (v1 -- work for initial landing)

Categories

(Firefox Build System :: Android Studio and Gradle Integration, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nalexander, Unassigned)

References

(Blocks 2 open bugs)

Details

(Keywords: meta)

This meta ticket tracks the bare minimum of work required to flip the switch and use --enable-gradle in automation to produce Fennec APKs that we ship to the Google Play Store.
Depends on: 1352599
Depends on: 1384312
No longer depends on: 1352599
Depends on: 1405396
Depends on: 1406457
Bug 1408083 isn't really a dependency of this work, but it does mean that some of the trickiest l10n interactions will not block this work.  That is, with the l10n single locale repacks going away almost immediately, we'll not need to keep a relatively complicated set of tasks working smoothly across the Gradle transition \o/
See Also: → 1408083
Depends on: 1408089
No longer depends on: 1408089
See Also: → 1408089
Depends on: 1411667
Blocks: 1414054
Wow, closing a meta ticket -- it's so rare!  The initial landing has, well, landed and stuck \o/
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Product: Firefox for Android → Firefox Build System
You need to log in before you can comment on or make changes to this bug.