Closed
Bug 1666434
Opened 4 years ago
Closed 4 years ago
[ESR68 EOL] remove all cron jobs and remaining running CI
Categories
(Release Engineering :: Release Automation: Other, task)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mtabara, Assigned: mtabara)
References
Details
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-esr68+
|
Details | Review |
Witb 78.3.0esr coming out today, esr68 is EOL officially. Its users are watershedding in Balrog to switch to esr 78.3.0. We need to make sure we're no longer running any sort of tasks there. That includes but not limited to:
- bouncer cron-jobs
- any of the cron entries in the
cron.yml
(bumper, periodic updates, etc) - searchfox should no longer take it into account
Unclear yet whether this is something that RelMan is taking care of or whether it falls under our jurisdiction. Filing this bug anyway to track any work to at least update our documentation.
Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Assignee: nobody → mtabara
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•4 years ago
|
||
Comment on attachment 9177109 [details]
Bug 1666434 - remove all cron jobs from esr68 because EOL. r=#releng
ESR Uplift Approval Request
- If this is not a sec:{high,crit} bug, please state case for ESR consideration: ESR68 is EOL. Kill all cron jobs from ESR68 going forward to not waste resources.
- User impact if declined:
- Fix Landed on Version:
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky):
- String or UUID changes made by this patch:
Attachment #9177109 -
Flags: approval-mozilla-esr68?
Comment 3•4 years ago
|
||
Comment on attachment 9177109 [details]
Bug 1666434 - remove all cron jobs from esr68 because EOL. r=#releng
Approved.
Attachment #9177109 -
Flags: approval-mozilla-esr68? → approval-mozilla-esr68+
Assignee | ||
Comment 4•4 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•