Closed
Bug 836036
Opened 12 years ago
Closed 12 years ago
Add MOZ_ESR lines to the mozconfig whitelist for comm-esr17
Categories
(Release Engineering :: Release Requests, defect)
Release Engineering
Release Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: standard8, Assigned: bhearsum)
References
Details
Attachments
(2 files, 1 obsolete file)
12.95 KB,
patch
|
jhopkins
:
review-
|
Details | Diff | Splinter Review |
12.92 KB,
patch
|
jhopkins
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
As we're building TB esr17 and TB mainstream 17 off of the same repository, we're using two sets of mozconfigs.
The esr ones have additional lines:
# Enable ESR branding
export MOZ_ESR=1
As we need to have either esr or release mozconfigs compared against nightly, we need to whitelist this line.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → bhearsum
Assignee | ||
Comment 1•12 years ago
|
||
I moved the mozconfig logic into a library so I could write this script that lets us compare w/out going through the hassle of release sanity. I tested with and without my whitelist changes, and adding my change to it shuts up verify_mozconfigs.
Attachment #708741 -
Flags: review?(jhopkins)
Assignee | ||
Comment 2•12 years ago
|
||
Attachment #708741 -
Attachment is obsolete: true
Attachment #708741 -
Flags: review?(jhopkins)
Attachment #708750 -
Flags: review?(jhopkins)
Comment 3•12 years ago
|
||
Comment on attachment 708750 [details] [diff] [review]
fix logging in mozconfig compare script
Unfortunately this patch is bitrotted already due to the pep8 reformatting change.
Attachment #708750 -
Flags: review?(jhopkins) → review-
Assignee | ||
Comment 4•12 years ago
|
||
Attachment #709055 -
Flags: review?(jhopkins)
Updated•12 years ago
|
Attachment #709055 -
Flags: review?(jhopkins) → review+
Assignee | ||
Comment 5•12 years ago
|
||
Comment on attachment 709055 [details] [diff] [review]
unbitrot
Worked for my staging tests, landed!
Attachment #709055 -
Flags: checked-in+
Assignee | ||
Updated•12 years ago
|
Status: NEW → 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
•