Closed
Bug 1339622
Opened 8 years ago
Closed 4 years ago
Tasks created by taskcluster-github should have a way of using caches in a safe way
Categories
(Taskcluster :: Services, defect, P5)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: garndt, Unassigned)
References
Details
Currently we do not by default allow tasks created from github events to use caches. There is a very good reason for it right now, the fact that we do not have paramterized roles. Caches should be scoped per repo to be prevent bad actors from polluting caches of another repo. To make this maintainable, repos using TaskCluster should have a paramterized role allowing for this.
This bug is to just keep it in mind that we want caches, but do not have an ability to allow for this just yet.
Reporter | ||
Updated•8 years ago
|
QA Contact: bstack
Comment 1•7 years ago
|
||
Dustin, now that we have parameterized roles, I guess we can implement this now?
Flags: needinfo?(dustin)
Updated•6 years ago
|
Priority: -- → P5
Updated•6 years ago
|
Component: Github → Services
Comment 4•4 years ago
|
||
I'm not sure why this wasn't possible before. But we now allow caches per-project, and projects can specialize those scopes as desired.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•