Closed
Bug 1488913
(rip-buildbot)
Opened 6 years ago
Closed 1 year ago
Decommission buildbot
Categories
(Release Engineering :: General, enhancement)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Unassigned)
References
Details
Now that ESR52 is EOL, we can retire buildbot, and all the supporting infrastructure.
RIP buildbot.
Reporter | ||
Updated•6 years ago
|
Alias: rip-buildbot
Comment 1•6 years ago
|
||
Please retain buildbot-master01 and buildbot-master77 for l10n bumper and releaserunner3, even if we cleanup their buildbot master and command + pulse queue handlers.
Comment 2•6 years ago
|
||
At CatLee's request, we will be delaying this task for now.
Reporter | ||
Comment 3•6 years ago
|
||
We can go ahead now!
Comment 4•6 years ago
|
||
For now we stopped Every buildbot-master found within AWS (USE1 and USW2), except 01 and 77. Also stopped buildbot-master69, 71, 73 and 75 from SCL3.
Comment 5•6 years ago
|
||
(In reply to Zsolt Fay [:zsoltfay] from comment #4)
> For now we stopped Every buildbot-master found within AWS (USE1 and USW2),
> except 01 and 77. Also stopped buildbot-master69, 71, 73 and 75 from SCL3.
Continued and stopped all the masters from SCL3, also disabled all the nagios checks and notifications.
Updated•1 year ago
|
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•