Closed
Bug 623222
Opened 15 years ago
Closed 14 years ago
the update xml for android is pushed out before the actual update
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: blassey, Assigned: mozilla)
Details
(Whiteboard: [release][automation])
Attachments
(1 file)
|
4.75 KB,
patch
|
nthomas
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
The problem is that if anything goes wrong with building or publishing the nightly, users constantly get offered a non-existent update.
Updated•15 years ago
|
Whiteboard: [release][automation]
| Assignee | ||
Updated•15 years ago
|
Assignee: nobody → aki
| Assignee | ||
Comment 1•15 years ago
|
||
Is there an example of this?
For nightlies, we:
a) build en-US
b) create en-US snippets
c) upload en-US
d) upload en-US snippets
e) repeat for multilocale
| Reporter | ||
Comment 2•15 years ago
|
||
While the multilocale repacks were broken, people were getting notifications that updates were available but the download failed because it wasn't available. I asked bear if we upload the updates.xml before the apk was uploaded, he said they might.
| Assignee | ||
Comment 3•15 years ago
|
||
We upload afterwards.
However, it's certainly possible we upload them whether the build was successful or not. I'll try to see what we can do to avoid that.
| Assignee | ||
Comment 4•14 years ago
|
||
I think we need to stop uploading en-US snippets. Pretty sure AUS doesn't distinguish between the en-US and multi installs.
Comment 5•14 years ago
|
||
What does a query to AUS for a multi-install look like ? An actual captured over the wire example. If it's expanding %LOCALE% as en-US for multi then I'm not surprised this is happening.
| Assignee | ||
Comment 6•14 years ago
|
||
* Don't create updates for en-US in a multilocale Android build
* The multi update snippet is uploaded after the apk, which is uploaded with haltOnFailure=True. So if we don't upload the apk successfully, we won't upload the snippet.
* Remove the outdated AndroidReleaseBuildFactory in 0.8. When we port mobile releases to 0.8 we would have overwritten this; having old unused code is confusing.
Attachment #510395 -
Flags: review?(nrthomas)
| Assignee | ||
Comment 7•14 years ago
|
||
Comment on attachment 510395 [details] [diff] [review]
port android multilocale update fixes from 0.7 to 0.8
Tested here:
http://staging-master.build.mozilla.org:8011/builders/Android%20R7%20mozilla-central%20nightly/builds/0
No update steps happened before the multil10n step; looks good.
Updated•14 years ago
|
Attachment #510395 -
Flags: review?(nrthomas) → review+
| Assignee | ||
Comment 8•14 years ago
|
||
Comment on attachment 510395 [details] [diff] [review]
port android multilocale update fixes from 0.7 to 0.8
http://hg.mozilla.org/build/buildbotcustom/rev/ab47536b72f7
Attachment #510395 -
Flags: checked-in+
| Assignee | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•