1357789 - Allow github.com/ochameau/ff-dt to use windows worker

Status: RESOLVED FIXED

(Taskcluster :: Operations and Service Requests, task)

Description

[Alexandre Poirot [:ochameau]]

github.com/ochameau/ff-dt is the work in progress repo for DevTools on github
(see bug 1356226)

I'm currently looking into getting DevTools tests to run on Windows:
https://github.com/ochameau/ff-dt/blob/reference/.taskcluster.yml#L88-L115
  workerType: "win2012r2"

But I don't have necessary scope to run on the windows workers.

Taskcluster bot tells me:
  In other words you are missing scopes from one of the options:
   * Option 0:
      - "queue:create-task:aws-provisioner-v1/win2012r2"

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

Pete, is this the right workerType for this usage?

Comment 2

[Pete Moore [:pmoore][:pete]]

tl;dr: Yes. :-)

win2012r2 is a general purpose Windows Server 2012 R2 environment, that should be suitable for most things. It is like our gecko builders, but under taskcluster control rather than releng control. It has some extra things like sshd, node, process explorer, process monitor, ... but doesn't necessarily keep up-to-date with all gecko changes that go on in gecko land.

If the environment needs to be a replica of the gecko builders we have, then gecko-1-b-win2012 is another option. Note though, that this would be using the same worker pool as the Windows gecko try builds, which may not be ideal from a security standpoint - therefore I think win2012r2 is the right choice. If something isn't suitable, we can always make changes, or add a new releng-managed worker type if it needs to be in line with the other gecko builders.

Comment 3

[Pete Moore [:pmoore][:pete]]

Created role: https://tools.taskcluster.net/auth/roles/#repo:github.com%252fochameau%252fff-dt:*

Alexandre, this should hopefully unblock you: if not, let me know!

Comment 4

[Alexandre Poirot [:ochameau]]

Thanks, it works like a charm!
I now have to make a correct set of commands for windows.

Comment 5

[Pete Moore [:pmoore][:pete]]

Great!

Here is the schema definition for the "payload" portion of the task definition for Windows (generic-worker) tasks:

  * https://docs.taskcluster.net/reference/workers/generic-worker/docs/payload

Let me know if you get stuck. There are some examples in gecko of course too (also nss).

Some of the more fully-features examples are in existing github integrations that run windows tasks are:

  * https://github.com/taskcluster/generic-worker/blob/master/.taskcluster.yml
  * https://github.com/taskcluster/taskcluster-worker/blob/master/.taskcluster.yml

Note, this page gives very useful information when setting up your github integration:

  * https://docs.taskcluster.net/reference/integrations/taskcluster-github/docs/usage

The nice thing about these integrations is they use a read only directory cache for the go compiler - so a nice example of how to get toolchains in your task without needing to download them on every run.

Don't hesitate to reach out if you get stuck. Good luck!

Comment 6

[Pete Moore [:pmoore][:pete]]

Just ni'ing you to make sure you get the info in command 5 ... :)

Comment 7

[Alexandre Poirot [:ochameau]]

Thanks for the links. I don't have much trouble with TaskCluster to be honest.
I surely have to ping you every once in a while about specifics, but looking at the various example on m-c and github.com helped me in most cases.

Now I'm fighting with msys/mingw32, which isn't the best environment to play with!