Open Bug 1163080 (partnerapk) Opened 5 years ago Updated 1 year ago

[meta] Build and deploy a dummy partner APK with alternate branding and optional distribution

Categories

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

defect

Tracking

(firefox40 affected)

Tracking Status
firefox40 --- affected

People

(Reporter: nalexander, Unassigned)

References

Details

(Keywords: meta)

Firefox for Android has a couple of build configurations intended for potential partners that aren't exercised in automation.  This ticket tracks the releng, build system, and product work to exercise those configurations.  The intention is to test unusual code paths, make it more clear how partner release integrations work, and provide a sandbox for reducing the work done in partner integrations.

The two paths we should start with are:

1) building with alternate branding.  The build system parts of this are well exercised by our Release/Beta/Aurora/Nightly channel builds, but for this build configuration we would like releng support for fetching remotely hosted branding.  That is, we'd like to clone a git (or hg, if it's easier) repo defining branding into a well-known location and refer to it during the build.  I think this requires mozharness changes these days.

2) building with a distribution [1].  The build system parts of this are non-existent -- ticket to follow -- but for this build configuration we would like to clone a repo defining distribution files and refer to it during the build.  Like the above.

I'll file additional tickets tracking pieces of this work as I understand them.

[1] https://wiki.mozilla.org/Mobile/Distribution_Files
Depends on: 1163082
> 2) building with a distribution [1].  The build system parts of this are
> non-existent -- ticket to follow -- but for this build configuration we
> would like to clone a repo defining distribution files and refer to it
> during the build.  Like the above.

Build system support is tracked in Bug 1163082.
Depends on: 1163084
(In reply to Nick Alexander :nalexander from comment #0)
> Firefox for Android has a couple of build configurations intended for
> potential partners that aren't exercised in automation.  This ticket tracks
> the releng, build system, and product work to exercise those configurations.
> The intention is to test unusual code paths, make it more clear how partner
> release integrations work, and provide a sandbox for reducing the work done
> in partner integrations.

I should add that this isn't intended to be private, and isn't intended to become a build for a particular partner.  It's intended to test and exercise pieces of Firefox for Android's partner-supporting technology.
margaret and rnewman have posted a sample distribution at https://github.com/mozilla/fennec-distribution-sample.
toonetown: you might be interested in some of this work, since you care about repacking with separate branding, etc.
Flags: needinfo?(nathan)
Thanks!  I am interested.
Flags: needinfo?(nathan)
NI to me to push on all sides of this.
Flags: needinfo?(nalexander)
(In reply to Nick Alexander :nalexander from comment #7)
> NI to me to push on all sides of this.

There's still build system work (Bug 1163082) but the NI isn't going to raise the priority of that work.
Flags: needinfo?(nalexander)
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195

Needinfo :susheel if you think this bug should be re-triaged.
Priority: -- → P5
Product: Firefox for Android → Firefox Build System
You need to log in before you can comment on or make changes to this bug.