Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Fennec Transition: Create product flavor for different producs #698

Closed
pocmo opened this issue Feb 27, 2019 · 0 comments
Closed

Fennec Transition: Create product flavor for different producs #698

pocmo opened this issue Feb 27, 2019 · 0 comments
Assignees
@pocmo

Comments

@pocmo
Copy link
Contributor

pocmo commented Feb 27, 2019 •
edited by data-sync-user
Loading

Meta: #662

To separate the migration code from the "pure"/"clean" Fenix build we want to have separate product flavors:

  • greenfield (pure Fenix without anything added)
  • firefoxNightly (To replace Firefox Nightly)
  • firefoxBeta (To replace Firefox Beta)
  • firefoxRelease (To replace Firefox Release)

┆Issue is synchronized with this Jira Task
@pocmo pocmo added the size S label Feb 27, 2019
@pocmo pocmo self-assigned this Feb 27, 2019
This was referenced Feb 27, 2019
Closed
Closed
Closed
Closed
Closed
pocmo added a commit to pocmo/fenix that referenced this issue Feb 27, 2019
@pocmo
Closes mozilla-mobile#698: Create product flavors for Fennec transition.
4b1c4b7 
* greenfield (pure Fenix without anything added)
* firefoxNightly (To replace Firefox Nightly)
* firefoxBeta (To replace Firefox Beta)
* firefoxRelease (To replace Firefox Release)

For now it will be a bit annoying to have all those flavors. But once the transition has been
successfully completed we can start to tear them down again.

If this is going to slow down the CI process then I might look into parallelizing the build
or potentially introducing a taskcluster CI setup (if that makes sense).
pocmo added a commit to pocmo/fenix that referenced this issue Feb 27, 2019
@pocmo
Closes mozilla-mobile#698: Create product flavors for Fennec transition.
76c0bd8 
* greenfield (pure Fenix without anything added)
* firefoxNightly (To replace Firefox Nightly)
* firefoxBeta (To replace Firefox Beta)
* firefoxRelease (To replace Firefox Release)

For now it will be a bit annoying to have all those flavors. But once the transition has been
successfully completed we can start to tear them down again.

Once GeckoView universal builds are available we can get rid of the "abi" dimension.

If this is going to slow down the CI process then I might look into parallelizing the build
or potentially introducing a taskcluster CI setup (if that makes sense).
pocmo added a commit to pocmo/fenix that referenced this issue Feb 27, 2019
@pocmo
Closes mozilla-mobile#698: Create product flavors for Fennec transition.
2ca272f 
* greenfield (pure Fenix without anything added)
* firefoxNightly (To replace Firefox Nightly)
* firefoxBeta (To replace Firefox Beta)
* firefoxRelease (To replace Firefox Release)

For now it will be a bit annoying to have all those flavors. But once the transition has been
successfully completed we can start to tear them down again.

Once GeckoView universal builds are available we can get rid of the "abi" dimension.

If this is going to slow down the CI process then I might look into parallelizing the build
or potentially introducing a taskcluster CI setup (if that makes sense).
@ghost ghost added in progress labels Feb 27, 2019
@ghost ghost removed in progress labels Feb 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pocmo pocmo

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pocmo