Closed Bug 1375175 Opened 8 years ago Closed 6 years ago

Roll out runAsWorkerUser to production-used OCC worker types (gecko-t-* and gecko-1-b-*)

Categories

(Taskcluster :: Workers, enhancement)

Product:
Taskcluster
Component:
Workers
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: pmoore, Unassigned)

References

Details

As I write this bug, I am beginning to question whether we really want generic-worker CI to run on our production gecko workers. Probably not. So I will probably resolve this as WONTFIX in the next days. But I'll still create this bug to at least track this topic, and also since others can jump in and share opinions too. Perhaps the better way of solving the how-to-maintain-so-many-workerTypes problem is to better separate AMI generation from worker types (one set of AMIs being usable by multiple worker types, which currently isn't possible in OCC but could be introduced) in combination with automated generation of worker type definitions (see https://github.com/taskcluster/taskcluster-rfcs/issues/62). I should have thought this through more carefully before going on a bug-creation spree. :D
QA Contact: pmoore
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Component: Generic-Worker → Workers
You need to log in before you can comment on or make changes to this bug.