Closed Bug 629528 Opened 15 years ago Closed 10 years ago

Android nightly update creation fails after bumping versions

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P5)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
ARM
Android
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mozilla, Unassigned)

References

Details

(Whiteboard: [mobile][updates])

This is directly tied to using the apk instead of a mar. The apk has a version number in it. Our nightly build logic says "download MY_APK_NAME from the latest nightly ftp directory, then extract previous buildid"; we can't download fennec 4.0b5pre when the previous nightly built a 4.0b4pre. Therefore I assert the *2nd* nightly of a particular version will successfully create update snippets.
Whiteboard: [android_tier_1]
Whiteboard: [android_tier_1]
per irc w/aki, this is nice to do, but does not block android from becoming tier1.
Severity: normal → enhancement
Component: Release Engineering → Release Engineering: Platform Support
Priority: P3 → P5
QA Contact: release → coop
Whiteboard: [mobile][updates]
Product: mozilla.org → Release Engineering
Still an issue?
Flags: needinfo?(aki)
That depends on how the balrog changes happened... if it happens before the upload instead of after, then not an issue; if it didn't change the order, then still an issue.
It appears the balrog steps haven't changed the order, so still an issue.
Flags: needinfo?(aki)
I'm guessing this is not an issue in the Mozharness script.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.