Closed
Bug 1431895
Opened 6 years ago
Closed 6 years ago
define a Buildduty day 1 and -1 checklist for getting access to various systems
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jlund, Unassigned)
Details
for Releng we have: https://wiki.mozilla.org/ReleaseEngineering/Day_1_Checklist Since Buildduty are going to take on more scope than releng, I think it is worth having a separate list. In addition to day 1, we should also have a last day list so we know what access needs to be revoked.
Reporter | ||
Comment 1•6 years ago
|
||
This is partly done: https://wiki.mozilla.org/Buildduty/day_1_checklist Working on last day checklist now.
Reporter | ||
Comment 2•6 years ago
|
||
(In reply to Jordan Lund (:jlund) from comment #1) > This is partly done: https://wiki.mozilla.org/Buildduty/day_1_checklist > > Working on last day checklist now. last day that can be used for both releng and buildduty: https://wiki.mozilla.org/ReleaseEngineering/Day_-1_Checklist
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•