Closed Bug 1184129 Opened 10 years ago Closed 10 years ago

Figure out nightly vs release l10n mozconfig differences

Categories

(Release Engineering :: Release Automation, defect)

Product:
Release Engineering
Component:
Release Automation
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rail, Assigned: rail)

References

Details

I just realized the we have the following hack in our current release script: http://hg.mozilla.org/build/tools/file/e3857f4deaba/lib/python/build/l10n.py#l70 mozconfig.write("ac_add_options --enable-official-branding") The mozharness script doesn't do anything like that, so we probably should find a way o set that properly. Maybe as a part of merge scripts.
Component: Mozharness → Release Automation
QA Contact: jlund → bhearsum
I think that's a release-only code path, and exists because we use browser/config/mozconfigs/*/l10n-mozconfig for all types of builds (dep/opt & release-style). Merge scripts sound like a reasonable way to fix that.
This should be fixed by bug 1184089 now
Assignee: nobody → rail
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.