Closed
Bug 602329
Opened 15 years ago
Closed 15 years ago
Need a way to switch update channels
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: mozilla, Unassigned)
Details
We weren't able to test the betatest channel due to this.
http://kb.mozillazine.org/Software_update says about:config doesn't work (it doesn't).
A way to change channels so we can test updates before pushing an update live will become very important once we're live.
Comment 1•15 years ago
|
||
QA normally changes <app>/defaults/pref/channel-prefs.js prior to starting the app. Is that available on Android ?
Comment 2•15 years ago
|
||
Fennec puts the app.update.channel in the <app>/defaults/preferences/mobile.js file, but on Android everything is bundled in the omnijar, so it's harder to extract-edit-repackage.
I noticed in the code that we could play a trick using the partner update channel:
http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/update/nsUpdateService.js#586
That is the code that gets the channel used in the AUS URL. The preference is read from the default branch, so even if you try to override "app.update.channel" in about:config, it won't work.
However, notice how we look for partner channel info too? We might be able to tweak the channel using about:config. Something like:
"app.partner.test" = "test"
would create a channel like:
"beta-cck-test"
Reporter | ||
Comment 3•15 years ago
|
||
Pushing to beta-cck-test and using app.partner.test = test worked.
We probably want to doc this for testers; I've got it in my build notes and probably want to automate it. But we definitely have a way to switch update channels.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Verified:
Mozille/5.0 (Android; Linux armv71; rv:2.0b7pre) Gecko20101006 Firefox/4.0b7pre Fennec/4.0b1
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 5•15 years ago
|
||
[13:38] <nthomas> the other option is to copy app.update.url to app.update.url.override and s/%CHANNEL%/betatest/
You need to log in
before you can comment on or make changes to this bug.
Description
•