Closed Bug 836036 Opened 10 years ago Closed 10 years ago

Add MOZ_ESR lines to the mozconfig whitelist for comm-esr17

Categories

(Release Engineering :: Release Requests, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: standard8, Assigned: bhearsum)

References

Details

Attachments

(2 files, 1 obsolete file)

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.
Blocks: 815302
Assignee: nobody → bhearsum
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)
Attachment #708741 - Attachment is obsolete: true
Attachment #708741 - Flags: review?(jhopkins)
Attachment #708750 - Flags: review?(jhopkins)
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-
Attached patch unbitrotSplinter Review
Attachment #709055 - Flags: review?(jhopkins)
Attachment #709055 - Flags: review?(jhopkins) → review+
Comment on attachment 709055 [details] [diff] [review]
unbitrot

Worked for my staging tests, landed!
Attachment #709055 - Flags: checked-in+
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.