Closed
Bug 1178282
Opened 9 years ago
Closed 8 years ago
adjust CI mozconfigs on release branches to create release builds
Categories
(Release Engineering :: Release Automation: Other, defect)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: jlund)
References
Details
We need the CI mozconfigs on release branches such as mozilla-beta to create release-able builds. This should be a pretty simple adjustment of copying stuff from the beta/release mozconfigs to the CI ones, such as: * Enabling PGO * Generating complete MARs * Building/publishing mar/mbsdiff We also talked briefly about whether or not we should ensure we're doing clobbers for release promotion CI builds, but didn't reach a decision. This work is likely to start off as living on the Date branch, where we'll be staging all of the release promotion changes.
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → jlund
Comment 1•8 years ago
|
||
Bug 1142231 shoudl address the SDK and MAR issues: + MOZ_AUTOMATION_UPDATE_PACKAGING=1 + MOZ_AUTOMATION_SDK=1 PGO should be probably enabled by using beta/release mozconfigs.
Comment 2•8 years ago
|
||
I think we are done with mozconfigs.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•