Closed
Bug 733694
Opened 12 years ago
Closed 12 years ago
Add tests for major update
Categories
(Release Engineering :: Release Automation: Other, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: nthomas)
References
Details
Attachments
(1 file)
179.47 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
We have major update code and PPC/Intel architecture detection which isn't being tested.
Assignee | ||
Comment 1•12 years ago
|
||
3.6.27 -> 10.0.2 major updates. Note the extra alias at the top of Firefox-10.0.2-build1.json to catch the old buildTarget using an otherwise-stock 10.0.2 blob. One typo fix to make major updates work.
Attachment #607040 -
Flags: review?(bhearsum)
Comment 2•12 years ago
|
||
Comment on attachment 607040 [details] [diff] [review] Major update tests Review of attachment 607040 [details] [diff] [review]: ----------------------------------------------------------------- ::: auslib/AUS.py @@ -208,4 @@ > # AUS2 snippets have a trailing newline, add one here for easy diffing > snippets[patch['type']] = "\n".join(snippet) + '\n' > - # XXX: need to handle old releases needing completes duplicating partials > - # add another parameter in the rule table and use it here Do we not need to handle duplicate partials anymore, or did this already get handled somewhere?
Attachment #607040 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 3•12 years ago
|
||
We should just set fakePartials in release blobs for 3.6 or older, and have a copy of later release blobs with it set for major updates from 3.6 or older (or make good on my idea to have a bag of properties attached to each rule rather than stuff them in release blobs).
Assignee | ||
Comment 4•12 years ago
|
||
Comment on attachment 607040 [details] [diff] [review] Major update tests https://github.com/mozilla/balrog/commit/57f104f218
Attachment #607040 -
Flags: checked-in+
Comment 5•12 years ago
|
||
(In reply to Nick Thomas [:nthomas] from comment #3) > We should just set fakePartials in release blobs for 3.6 or older, and have > a copy of later release blobs with it set for major updates from 3.6 or > older (or make good on my idea to have a bag of properties attached to each > rule rather than stuff them in release blobs). Sounds good either way.
Comment 6•12 years ago
|
||
Bulk move of bugs to Release Automation component.
Component: Release Engineering: Automation (General) → Release Engineering: Automation (Release Automation)
Flags: checked-in+
Assignee | ||
Comment 7•12 years ago
|
||
PPC/Intel stuff farmed out to bug 757321.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•