Closed Bug 1412347 Opened 7 years ago Closed 7 years ago

switch away from callek/update-test-runner2 for update verify

Categories

(Release Engineering :: Release Automation: Other, enhancement, P1)

Product:
Release Engineering
Component:
Release Automation: Other
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1391983

People

(Reporter: bhearsum, Unassigned)

Details

(Whiteboard: [releaseduty])

While working on some update verify changes I noticed that we use a Docker image for them that only Callek has access to. This means that he's a single point of failure if we need to change it. We should switch to a centrally-owned one, that many people have credentials to.
Priority: -- → P1
Whiteboard: [releaseduty]
(In reply to Ben Hearsum (:bhearsum) from comment #0) > While working on some update verify changes I noticed that we use a Docker > image for them that only Callek has access to. This means that he's a single > point of failure if we need to change it. We should switch to a > centrally-owned one, that many people have credentials to. I had :rail listed as a collaborator on this docker image, I've also just added bhearsum. So at least I'm not a single-point-of-failure.
Might be worth adding some european folks for releaseduty coverage backup as well to not block a release until ET morning if things go south.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
I also just now added :mtabara as suggested
You need to log in before you can comment on or make changes to this bug.