+++ This bug was initially created as a clone of Bug #1529937 +++

Here's a short list of worker types:

gecko-*-b-win2012
gecko-t-win7*
gecko-t-win10*

See https://taskcluster-web.netlify.com/provisioners/aws-provisioner-v1 for a more exhaustive list.

Like linux, the test images (e.g. gecko-t-win7-32-gpu) are an unknown quantity because they require a desktop environment in which to run tests, and the Google environment (particularly around GPUs) may be quite different. If these images warrant more work to (re)create, i.e. the images require non-trivial updates, we should split them out into their own bug(s).

Kendall: should there be a separate dependency here on relops getting Windows imaging working in GCE? I'm not sure where we left that after the all-hands. Do we already have a bug on file for that?

(In reply to Chris Cooper [:coop] pronoun: he from comment #0)

See https://taskcluster-web.netlify.com/provisioners/aws-provisioner-v1 for a more exhaustive list.

Pete: should we be looking to move the other non-Firefox-CI Windows workers, i.e. servo-win2016 and nss-win2012r2?

(In reply to Chris Cooper [:coop] pronoun: he from comment #1)

Kendall: should there be a separate dependency here on relops getting Windows imaging working in GCE? I'm not sure where we left that after the all-hands. Do we already have a bug on file for that?

We do now. Once the VPNs are up, I'll have Rob start.

(In reply to Chris Cooper [:coop] pronoun: he from comment #2)

(In reply to Chris Cooper [:coop] pronoun: he from comment #0)

See https://taskcluster-web.netlify.com/provisioners/aws-provisioner-v1 for a more exhaustive list.

Pete: should we be looking to move the other non-Firefox-CI Windows workers, i.e. servo-win2016 and nss-win2012r2?

Once we have a provisioner / worker manager for GCP, we should be able to migrate worker type definitions and create an machine-image publishing mechanism for GCP.

Note, the servo machine images are created by servo team directly, and they make them readable by the taskcluster AWS account, and update the AWS provisioner worker type definitions themselves (they now also have a staging servo win 2016 worker type). So servo is quite a self-serve success story whereby we aren't really involved.

We could potentially move nss-win2012r2 and win2012r2 and deepspeech-win once we have a provisioning solution in GCP; I wouldn't propose setting up a static pool for these worker types due to the load being quite bursty.