make the workerTypes in-tree consistent under a single config umbrella
Categories
(Release Engineering :: General, enhancement)
Tracking
(Not tracked)
People
(Reporter: mtabara, Unassigned)
References
Details
While working in GCP migration, we've noticed there's some inconsistencies across workerTypes. In beetmoverworkers, they are mostly centralized in TODO (see https://phabricator.services.mozilla.com/D45045) while for bouncerworkers, they are all scattered everywhere (https://phabricator.services.mozilla.com/D45834)
Once we switched all GCP workers, we should look into cleanup and centralizing all those configs under the same roof, for consistency. Well, could be done whilst at it too, it's not blocking anyway.
|
||
Comment 1•5 years ago
|
||
We were thinking we should put worker alises in the kind.yml, and expand via ci/config.yml aliases.
|
Reporter | |
Comment 2•5 years ago
|
||
(In reply to Aki Sasaki [:aki] (he/him) (UTC-7) from comment #1)
We were thinking we should put worker alises in the kind.yml, and expand via ci/config.yml aliases.
That seems like a good idea.
|
|
Reporter | |
Updated•5 years ago
|
|
|
||
Comment 3•2 years ago
|
||
We've hit some level of consistency for the kubernetes workers, and we're continuing to move in that direction for the macs.
Description
•