(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #2)
the regular windows hardware machines would be ideal. Do you want to push to try using a special hardware type? we could have a mini pool that you could use.
Otherwise the loaners would be remote desktop to the machine, run the job manually which is not always straightforward. I have done that a lot before and once setup it is ok.
If you want 10 machines setup with a different hardware ID that taskcluster would use given that your try pushes have a custom hack in taskcluster (here is an example for testing windows 1903 on the VMs: https://hg.mozilla.org/try/rev/e45cad8128b62308ad4a7196c851e8f66ec0cd97 ), ask for that instead.
Otherwise, lets get a machine reserved for each of you and we can set up scripts that reduce the typing needed for testing new builds/tooling.
Hi Joel -- thanks for being so responsive. As per https://bugzilla.mozilla.org/show_bug.cgi?id=1562991#c3, we want exactly the same Win 10 configuration as Raptor currently runs. So hopefully no difficult imaging/configuration changes are needed.
In terms of loaners vs. a small pool, my personal preference would be a tiny pool (like 2 machines, say) rather than loaners. If we were "guaranteeed" to have jobs start in minutes, then it's a lot less hassle to push things to try for testing (which is what rwood and other experienced folks are basically always doing) than to have to work through the non-standard "loaner" configuration. That is, it's the slow decision task -> job completion that really drags down the progress loop. (Although iterating at a thing that could be done easily with interactive access can be frustrating too.) It seems like it would be much cheaper and easier to have a "Fast Pass" system where designated developers can hop the queue for a short time and trust the honor system for them to keep the number of such jobs down rather than stand up a tiny pool for focused effort of this sort, but that's your call to make.