Closed
Bug 725303
Opened 13 years ago
Closed 13 years ago
--enable-official-branding should be in the release mozconfig only whitelist
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: mozilla)
References
Details
(Whiteboard: [automation][releases])
Attachments
(2 files)
8.58 KB,
patch
|
bhearsum
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
19.23 KB,
patch
|
lsblakk
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
We don't use this flag for anything but release builds.
2012-02-08 05:31:05,488 : ERROR : not in release mozconfig's whitelist (releases/mozilla-release/win32/nightly) : ac_add_options --enable-official-branding
Updated•13 years ago
|
Assignee: nobody → lsblakk
Comment 1•13 years ago
|
||
The flag appears to be useless with latest code, fx-10 built with --disable-officia-branding are still built with branding icons, I have also tested the current beta build and still see official branding icons and naming.
Comment 2•13 years ago
|
||
Comment 1 isn't relevant to this bug (and I'm pretty sure it's also inaccurate and/or a misunderstanding).
Updated•13 years ago
|
Assignee: lsblakk → aki
Assignee | ||
Comment 4•13 years ago
|
||
This isn't strictly required, but it made my local testing a lot less noisy by letting me specify -l to skip the l10n dashboard checks.
Attachment #602193 -
Flags: review?(bhearsum)
Assignee | ||
Comment 5•13 years ago
|
||
Tested against release-firefox-mozilla-{release,beta,esr10}.py.
* removed trailing whitespace
* removed old mobile platforms (maemo, linux-desktop, linux-android from non-esr10 branches)
* added the -j4 line to the branches
* added esr10 to the whitelist
* key off the branch_name instead of branch in the whitelist dict (fixed the --official-branding problem)
This patch is meant to apply on top of the patch in bug 725300 and the checkL10n patch in this bug, but may apply without them.
Attachment #602194 -
Flags: review?(lsblakk)
Reporter | ||
Comment 6•13 years ago
|
||
Comment on attachment 602193 [details] [diff] [review]
add -m and -l options to release_sanity.py to skip mozconfig and l10n dashboard checking
Review of attachment 602193 [details] [diff] [review]:
-----------------------------------------------------------------
Thanks a ton for doing this!
Attachment #602193 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 7•13 years ago
|
||
Comment on attachment 602193 [details] [diff] [review]
add -m and -l options to release_sanity.py to skip mozconfig and l10n dashboard checking
http://hg.mozilla.org/build/tools/rev/0789913f53fc
Attachment #602193 -
Flags: checked-in+
Comment 8•13 years ago
|
||
Comment on attachment 602194 [details] [diff] [review]
get firefox mozconfig checks to 0 errors
looks good, hope the next run is smooth!
Attachment #602194 -
Flags: review?(lsblakk) → review+
Assignee | ||
Comment 9•13 years ago
|
||
Comment on attachment 602194 [details] [diff] [review]
get firefox mozconfig checks to 0 errors
http://hg.mozilla.org/build/tools/rev/34e5ef632769
Attachment #602194 -
Flags: checked-in+
Assignee | ||
Comment 10•13 years ago
|
||
Firefox release_sanity mozconfig runs should be clean now.
Fennec is still open in bug 725294.
Status: NEW → RESOLVED
Closed: 13 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
•