This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
Make *GreenfieldRaptorRelease builds not use org.mozilla.fenix application ID
#1566
Labels
eng:automation
Build automation, Continuous integration, ..
eng:task
An engineering breakout issue of a user story
Comments
mitchhentges
pushed a commit
to mitchhentges/fenix
that referenced
this issue
May 1, 2019
mitchhentges
pushed a commit
to mitchhentges/fenix
that referenced
this issue
May 1, 2019
mitchhentges
pushed a commit
to mitchhentges/fenix
that referenced
this issue
May 1, 2019
mitchhentges
pushed a commit
to mitchhentges/fenix
that referenced
this issue
May 1, 2019
mitchhentges
pushed a commit
to mitchhentges/fenix
that referenced
this issue
May 1, 2019
mitchhentges
pushed a commit
to mitchhentges/fenix
that referenced
this issue
May 2, 2019
mitchhentges
pushed a commit
to mitchhentges/fenix
that referenced
this issue
May 2, 2019
mitchhentges
pushed a commit
to mitchhentges/fenix
that referenced
this issue
May 2, 2019
data-sync-user
changed the title
org.mozilla.fenix application IDorg.mozilla.fenix application ID
data-sync-user
changed the title
org.mozilla.fenix application IDorg.mozilla.fenix application ID
data-sync-user
changed the title
org.mozilla.fenix application IDorg.mozilla.fenix application ID
data-sync-user
changed the title
org.mozilla.fenix application IDorg.mozilla.fenix application ID
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Post #1321, we can finally use the (greenfield) Raptor release builds. But they use the
org.mozilla.fenixapplication ID and are signed with a special "dep" key. That means you can't pave over your existingorg.mozilla.fenixNightly vehicle, making it very difficult to do automation testing and dogfood Fenix at the same time.Let's make the Raptor/automation builds have a different application ID.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: