Open
Bug 2073107
Opened 2 months ago
Updated 1 month ago
rebuilding partner builds between promote and push phases of a release causes the wrong to be shipped
Categories
(Release Engineering :: Release Automation, defect, P3)
Release Engineering
Release Automation
Tracking
(Not tracked)
NEW
People
(Reporter: bhearsum, Unassigned)
References
(Blocks 2 open bugs)
Details
When we build a release RC we pick up whatever partner build manifests and data that happen to exist at that time. If those are updated after that point, and we rebuild them by hand, we end up shipping the ones that were built with the RC rather than the updated ones.
https://bugzilla.mozilla.org/show_bug.cgi?id=1943594#c3 relates to this a bit, and https://bugzilla.mozilla.org/show_bug.cgi?id=2071455 is a specific case where this happened. The "fix" in that case was to manually ship the updated repacks after the RC had shipped, which meant there was a point in time where the wrong partner builds were live.
Updated•1 month ago
|
Severity: -- → S3
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•