Closed Bug 594219 Opened 11 years ago Closed 11 years ago

release updates for android

Categories

(Release Engineering :: General, defect)

ARM
Android
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aki, Assigned: aki)

References

Details

Attachments

(2 files, 4 obsolete files)

Once we enable nightly updates for Android, we need to also enable them for releases in time for 2.0b1.

This has the added complexity of nightlies-on-0.8.0, releases-on-0.7.x.
Status: NEW → ASSIGNED
Is patcher2 + backupsnip/pushsnip mainly to deal with the large matrix of platforms x locales?  Do the snippets themselves actually differ?

Asking because I'm going the "just generate snippets for android en-US for 2.0b1" route and am hoping that that will be minimal in terms of manual steps afterwards to push to the beta test and beta channels during release time.
(In reply to comment #1)
> Is patcher2 + backupsnip/pushsnip mainly to deal with the large matrix of
> platforms x locales?  Do the snippets themselves actually differ?

Yes and yes. The file sizes and hashes are different for every platform + locale combination. Once you have several older releases there is duplication, but you don't have to worry about that yet.

> Asking because I'm going the "just generate snippets for android en-US for
> 2.0b1" route and am hoping that that will be minimal in terms of manual steps
> afterwards to push to the beta test and beta channels during release time.

Manual steps would be simple if you only have only one locale and only need a complete snippet. Do you mean 2.0b1 -> 2.0b2 updates ? I thought 2.0a1 wasn't updateable.
(In reply to comment #2)
> (In reply to comment #1)
> > Is patcher2 + backupsnip/pushsnip mainly to deal with the large matrix of
> > platforms x locales?  Do the snippets themselves actually differ?
> 
> Yes and yes. The file sizes and hashes are different for every platform +
> locale combination. Once you have several older releases there is duplication,
> but you don't have to worry about that yet.

I meant, "Do the [release] snippets themselves actually differ [from nightly snippets]?"

I mean, the sum/size will be for a release build instead of a nightly build, and it'll point to the release url rather than the nightly url, but other than that?

Tried logging into aus2-staging but have not yet been successful, or I would have looked for myself.

> > Asking because I'm going the "just generate snippets for android en-US for
> > 2.0b1" route and am hoping that that will be minimal in terms of manual steps
> > afterwards to push to the beta test and beta channels during release time.
> 
> Manual steps would be simple if you only have only one locale and only need a
> complete snippet. Do you mean 2.0b1 -> 2.0b2 updates ? I thought 2.0a1 wasn't
> updateable.

Correct.  2.0b2 will have l10n, but the only updateable release build out there will be Android 2.0b1 en-US -> 2.0b2 en-US.

However, I'm going to try to test a staging Android release -> a 2nd staging Android release update so we know it works... doing so before 2.0b1 goes out the door would be ideal, if it's doable.
(In reply to comment #3)
> I meant, "Do the [release] snippets themselves actually differ [from nightly
> snippets]?"

Oh right. The format is unchanged, except for desktop Firefox adding
  detailsUrl=http://www.mozilla.com/en-US/firefox/4.0b5/releasenotes/
which is used for a 'Details' link on the update dialogs shown to users (and possibly elsewhere, rs would know). Bug 595384 says the desktop UI isn't being used so that may not apply here.
Blocks: 595977
I think I have enough here to force complete snippets for android release builds... staging run incoming.
This is pretty much the 080 patch for nightlies (bug 554249) except a) it's for the default 07x branch, and b) I split out the CreateCompleteUpdateSnippet() call to _createSnippet() so I could override it in AndroidReleaseBuildFactory.

Not sure if this will work properly; will see in staging.
Ok, those patches a) put the filepath in as the url instead of the url, and b) don't upload the snippet.

I'll fix that in a bit.
not yet tested; i'll put it through staging.
Attachment #474871 - Attachment is obsolete: true
Attachment #474873 - Attachment is obsolete: true
I'll have to add the old* prefs so we can upload the complete snippet to the previous release's aus dir.
This is tested; it uploaded the complete snippet to the previous release's betatest dir:
  /opt/aus2/incoming/3/Fennec/2.0a1/Android_arm-eabi-gcc3/20100825115329/en-US/betatest

Staging only.
Attachment #475247 - Attachment is obsolete: true
Attachment #477348 - Flags: review?(nrthomas)
I ported over the nightly (buildbot-0.8.0) changes, but had to change doStepIf to just warnOnFailure.

Added release-specific upload bits as well.
I had a successful build 8 of android-r7_build on sm01.
Attachment #475249 - Attachment is obsolete: true
Attachment #477350 - Flags: review?(nrthomas)
I ran two staging release builds for Android, a staging 2.0b1 and a staging 2.0b2.

The staging 2.0b2 run created the complete snippet for the 2.0b1 build in the betatest channel, which worked when we hit the url

http://staging-stage.build.mozilla.org/update/4/Fennec/2.0b1/20100924131121/Android_arm-eabi-gcc3/en-US/betatest/Linux%202.6.33.2-cyanogenmod/default/default/2.0b6pre/update.xml

in a browser.  I'm currently trying to get this Tegra configured to be able to test the update on device.
Semi-unborked my phone, but am getting a black screen (Android 2.1, Samsung Galaxy S Captivate) when launching Fennec.

Also tried on my 2.1 Tegra, which is headless, which provides different challenges.
Any chance for a review here?
Comment on attachment 477350 [details] [diff] [review]
android release updates -- custom (default)

For release it isn't necessary to create the empty snippets in a dir for the new build, but I don't think it does any harm to do so.
Attachment #477350 - Flags: review?(nrthomas) → review+
Comment on attachment 477348 [details] [diff] [review]
android release staging updates -- configs

Looks fine, except the milestone is probalby out of date now.
Attachment #477348 - Flags: review?(nrthomas) → review+
Comment on attachment 477350 [details] [diff] [review]
android release updates -- custom (default)

http://hg.mozilla.org/build/buildbotcustom/rev/dadaef9623c8
Attachment #477350 - Flags: checked-in+
This'll show up in 4.0b1 build1.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.