Closed
Bug 1391983
Opened 7 years ago
Closed 7 years ago
update verification use Docker image from user account instead of RelEng one
Categories
(Release Engineering :: Release Automation: Other, enhancement, P1)
Release Engineering
Release Automation: Other
Tracking
(firefox58 fixed)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox58 | --- | fixed |
People
(Reporter: mtabara, Assigned: bhearsum)
References
Details
(Whiteboard: [releaseduty])
Attachments
(1 file)
(deleted),
patch
|
rail
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
https://mozilla-release-logs.s3.amazonaws.com/mozilla-beta/firefox-56.0b4/build4/linux64_beta_update_verification_3_12-linux64-YuclPrMTQqODg2eQc6fnpw-1
says right at the beginning:
...
Status: Downloaded newer image for callek/update-test-runner2:latest
[taskcluster 2017-08-19 16:53:41.042Z] === Task Starting ===np
....
We are gradually trying to fix this and use RelEng generic accounts instead of user accounts for busfactor++ and fixing emergencies.
Reporter | ||
Comment 2•7 years ago
|
||
From bug 1412347 comment 1 Callek says: "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-po´int-of-failure". Might be worth adding other folks there too from Europe just as releaseduty backups.
Status: NEW → RESOLVED
Closed: 7 years ago
Priority: P3 → P1
Resolution: --- → FIXED
Reporter | ||
Comment 3•7 years ago
|
||
Accidentally closed this. We need to track further work here.
Thanks for the heads-up Callek!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 4•7 years ago
|
||
Callek added me as well as short-term change. As he suggested, and I fully agree, the long-term solution might be in-tree image.
Assignee | ||
Comment 5•7 years ago
|
||
We should probably switch this to be built from a Dockerfile too. As I understand it, it is manually updated at the moment. When I created my own version and did some manual updates, I ended up breaking the command somehow -- this sort of thing is likely to happen in production at some point too if we continue doing it by hand.
Assignee | ||
Comment 6•7 years ago
|
||
I think I'm going to need to fix this as part of my work for bug 1398793.
Assignee: nobody → bhearsum
Updated•7 years ago
|
Assignee | ||
Comment 7•7 years ago
|
||
I did tests for all target platforms with an image built from this Dockerfile:
https://tools.taskcluster.net/groups/Xoxq0DhDS52QaeuQGPBbrQ/tasks/Xoxq0DhDS52QaeuQGPBbrQ/runs/0
https://tools.taskcluster.net/groups/ThtN0-ZjS0e84Nnhr_64tg/tasks/ThtN0-ZjS0e84Nnhr_64tg/runs/0
https://tools.taskcluster.net/groups/MxaXG7oeTZmexBhmd0C6Mg/tasks/MxaXG7oeTZmexBhmd0C6Mg/details
https://tools.taskcluster.net/groups/EiHFCHVjQESkLpw530eR-w/tasks/EiHFCHVjQESkLpw530eR-w/details
https://tools.taskcluster.net/groups/QBwZos8iSDCD4uKnloIyKg/tasks/QBwZos8iSDCD4uKnloIyKg/runs/0
This will go unused until we change releasetasks to make use of it.
Attachment #8923538 -
Flags: review?(rail)
Updated•7 years ago
|
Attachment #8923538 -
Flags: review?(rail) → review+
Pushed by bhearsum@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/5f4f5a2b229d
add docker image for update verify. r=rail
Assignee | ||
Updated•7 years ago
|
Attachment #8923538 -
Flags: checked-in+
Comment 9•7 years ago
|
||
bugherder |
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
status-firefox58:
--- → fixed
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•