Closed Bug 1210181 Opened 6 years ago Closed 6 years ago

Allow ahal to use a custom quay.io image

Categories

(Taskcluster :: Operations and Service Requests, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: selenamarie, Assigned: garndt)

Details

This from IRC: 

14:29 <        ahal> | can anyone help me get TC try jobs to use a custom "tester" image? I tried changing the REGISTRY to 'quay.io/ahal' and uploading the modified image there, but then the decision task fails with this error: 
          https://s3-us-west-2.amazonaws.com/taskcluster-public-artifacts/DPo1XAwnTUqTizgufjBGzg/3/public/logs/live_backing.log
14:29 <        ahal> | "Error: You didn't give the task-graph scopesallowing it define tasks on the queue"
14:30 <        ahal> | and {"message":"Authorization Failed","error":{"info":"None of the scope-sets was satisfied"


I believe we just need to add docker-worker:image:quay.io/ahal/* to the scopes in mozilla-taskcluster.  

Are there any issues with that?
Fwiw, I just need a way to test changes to the image on try, it doesn't have to be on my quay.io account. If there's some other process in place that I don't know about, that would work for me too.
Hey Greg, what's the best way to test out image changes on try?
Flags: needinfo?(garndt)
I just pushed changes that should allow any image to be used on try.  Could you please try it out again with a new try push?
Flags: needinfo?(garndt)
Thanks, it worked! (I think):
https://treeherder.mozilla.org/#/jobs?repo=try&revision=ed62286e102c

At least the decision task isn't busted anymore.
Thanks, I confirmed it's picking up my custom quay.io image.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Assignee: nobody → garndt
Component: Service Request → Operations and Service Requests
You need to log in before you can comment on or make changes to this bug.