Creating and managing new worker types for Servo

RESOLVED FIXED

Status

task
RESOLVED FIXED
8 months ago
4 months ago

People

(Reporter: SimonSapin, Assigned: dustin)

Tracking

Details

Reporter

Description

8 months ago
Today we’ve landed a new decision task for Servo, and will start gating pull request on Taskcluster results. It all works great with servo-docker-worker.

Add we add Taskcluster support for more platforms (Windows, macOS, emulated Android) we’ll likely need multiple new worker types. To avoid going through requests like this every time, would it make sense to grant to Servo admins (role project-admin:servo) the scopes necessary to create and manage new worker types?

This would be:

* The servo-* namespace for worker types in the AWS provisioner, including ec2-manager:manage-resources:servo-* (like in bug 1492123)

* Any worker type in a new Servo-specific provisioner for non-AWS "bring your own worker" worker types. According to [1] this should be named proj-servo, but in [2] this convention doesn’t seem to be used in practice.

[1] https://docs.taskcluster.net/docs/manual/design/namespaces#provisioner-ids
[2] https://tools.taskcluster.net/provisioners/
Assignee: nobody → dustin
Most of those provisioners were invented before the convention.  There is proj-autophone :D
I updated https://tools.taskcluster.net/auth/roles/project%3Aservo%3Agrants%2Fservo-workers to contain the relevant scopes.  Let me know if something's missing!
Status: NEW → RESOLVED
Last Resolved: 8 months ago
Resolution: --- → FIXED
Component: Service Request → Operations and Service Requests
Product: Taskcluster → Taskcluster
You need to log in before you can comment on or make changes to this bug.