Closed
Bug 1304373
Opened 8 years ago
Closed 7 years ago
Simulate beta1 release builds by regularly merging aurora to jamun
Categories
(Release Engineering :: Release Automation: Other, defect, P3)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: rail, Assigned: mtabara)
References
Details
To prevent "OMG Beta1" issues we should start regularly uplift aurora to jamun and run release builds. We can use https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/scripts/merge_day/gecko_migration.py with a config like https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/configs/merge_day/aurora_to_beta.py The script should be modified to skip any manipulation of the "from" repo, such as tagging in https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/scripts/merge_day/gecko_migration.py#489-492, pushing https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/scripts/merge_day/gecko_migration.py#182, etc. These actions should be configurable. Also, it'd be great to separate pull and push URLs, so we pull using https:// (and the corresponding bundles) and push to ssh://. Mihai volunteered, thank you!
Reporter | ||
Updated•7 years ago
|
Priority: -- → P3
Assignee | ||
Comment 2•7 years ago
|
||
Found in triaging. Aurora is dead, long live Dawn! https://github.com/mozilla/releasewarrior/blob/master/how-tos/setup-staging-release.md describes how to perform staging releases. We are now doing these as part of releaseduty. Closing this bug.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•