Closed
Bug 1467456
Opened 7 years ago
Closed 7 years ago
periodic file updates on beta/esr60 need repo path fixing
Categories
(Release Engineering :: Release Automation, defect)
Release Engineering
Release Automation
Tracking
(firefox-esr60 fixed, firefox61 fixed, firefox62 fixed)
RESOLVED
FIXED
People
(Reporter: sfraser, Assigned: sfraser)
Details
Attachments
(1 file)
The repository path is assumed to be hg.mozilla.org/BRANCH, when it might be releases/BRANCH or projects/BRANCH.
Take this opportunity to condense the commit messages, as squashed commits confuse phabricator.
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → sfraser
Comment 1•7 years ago
|
||
1. Updated hgrepo to work with mozilla-beta, mozilla-esr60 and project branches (just in case)
2. Presquashed commits, so we only submit one.
3. Replaced 'which' with 'command -v' to avoid future shellcheck issues.
Comment 2•7 years ago
|
||
Comment on attachment 8984128 [details]
Bug 1467456 Use correct hg repo in repo-update r=ryanvm
Lisa Guo [:lguo] EST has approved the revision.
https://phabricator.services.mozilla.com/D1582
Attachment #8984128 -
Flags: review+
Pushed by sfraser@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c1197954d1b2
Use correct hg repo in repo-update r=lguo
Comment 4•7 years ago
|
||
bugherder |
Comment 5•7 years ago
|
||
bugherder uplift |
https://hg.mozilla.org/releases/mozilla-beta/rev/7679eddb8fdb
Note that Beta/ESR60 don't have bug 1451040 et al on it. Rather than trying to rebase this patch around that (would have been a giant mess), I just took periodic_file_updates.sh wholesale as it existed on m-c. Having discussed this with Simon, this should be reasonably safe since the remote-settings code won't be invoked by anything on those branches anyway, so it's effectively dead code (and probably less risky in the end than trying to rebase around it all).
status-firefox61:
--- → fixed
Comment 6•7 years ago
|
||
bugherder uplift |
status-firefox-esr60:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•