1330767 - Missing scope to create Taskcluster task/hook

Status: RESOLVED FIXED

(Taskcluster :: General, defect)

Description

[Bastien Abadie [:bastien]]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20161209094039

Steps to reproduce:

I created a Taskcluster hook for the project Shipit Dashboard (example: https://tools.taskcluster.net/hooks/#project-shipit/services-staging-shipit_dashboard-bot); but the task cannot run as my client needs an extra scope: queue:create-task:aws-provisioner-v1/releng-task

I only have ueue:create-task:aws-provisioner-v1/tutorial


Actual results:

The task did not execute.


Expected results:

The task should execute and run shipit-bot from the provided docker image.

Comment 1

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

Rok, is it OK for this hook to use the releng-task workerType?

Comment 2

[Rok Garbas [:garbas]]

:dustin: +1

Comment 3

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

OK, I added
  https://tools.taskcluster.net/auth/roles/#hook-id:project-shipit%252fservices-staging-shipit_dashboard-bot

should be good to go!

Comment 4

[Bastien Abadie [:bastien]]

Thanks Dustin, it works fine. 
But now i need to access Taskcluster Cache [1], so i also need this scope:

> releng-task:cache:shipit-bot-staging

I think this is the right scope given that the worker for this hook is releng-task. According to the documentation, it should otherwise be:

> docker-worker:cache:shipit-bot-staging


[1]: https://docs.taskcluster.net/reference/workers/docker-worker/caches

Comment 5

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

It's the second one you need.  Done:

https://tools.taskcluster.net/auth/roles/#hook-id:project-shipit%252fservices-staging-shipit_dashboard-bot