[docker-worker] Support reading workerType secrets from taskcluster-secrets service
Categories
(Taskcluster :: Workers, enhancement)
Tracking
(Not tracked)
People
(Reporter: pmoore, Assigned: pmoore)
References
Details
Attachments
(1 file)
Assignee | ||
Updated•8 years ago
|
Comment 1•7 years ago
|
||
Updated•6 years ago
|
Assignee | ||
Comment 2•6 years ago
|
||
Updated•6 years ago
|
Assignee | ||
Comment 3•6 years ago
|
||
Not ready for review yet, but I've started work on the code changes.
Will flag for review as soon as CI is passing and I'm confident the changes are correct...
Assignee | ||
Comment 4•6 years ago
|
||
Updated•6 years ago
|
Assignee | ||
Comment 5•6 years ago
|
||
I've deployed on ami-test and removed the worker type secrets from the worker type definition.
The worker successfully ran task E7ggXxODRvSZuLVQZFzcag, with working live logs, which implies it could successfully retrieve the livelog configuration from the worker type secret in the taskcluster secrets service.
Assignee | ||
Comment 6•6 years ago
|
||
Running a mozilla-central linux64 build for a sanity check:
This is just a modified task copied from mozilla-central on treeherder, with the treeherder metadata removed, and the worker type changed to ami-test
.
Assignee | ||
Comment 7•6 years ago
|
||
The linux64 job ran successfully, and :wcosta merged the PR.
Still need to make a docker-worker release.
Roll out to all docker-worker worker types is in bug 1375192.
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Comment 8•6 years ago
|
||
For the record, with Pete's help, I created/updated all secrets matching: worker-type:aws-provisioner-v1/mobile-*
[1]. This was causing workers to not spin up. I also cleaned the secrets
section in the worker definition, by leaving an empty dictionary[2].
[1] For instance: https://tools.taskcluster.net/secrets/worker-type%3Aaws-provisioner-v1%2Fmobile-3-b-ref-browser
[2] For instance: https://tools.taskcluster.net/aws-provisioner/mobile-3-b-ref-browser/view
Description
•