Closed Bug 1389714 Opened 7 years ago Closed 4 years ago

Allow variable with all scopes in expression language

Categories

(Taskcluster :: Services, enhancement, P5)

Product:
Taskcluster
Component:
Services
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: jonasfj, Unassigned, Mentored)

References

(Blocks 1 open bug)

Details

(Keywords: good-first-bug)

Right now we have to explicitly list all scopes in github decision tasks, because there is no role... we always have 3 different roles. I suggest a variable called "scope" which is either: assume:repo:github.com/<org>/<repo>:pull-request assume:repo:github.com/<org>/<repo>:branch:<branch> assume:repo:github.com/<org>/<repo>:release depending on the context. So it's easy to pass on exactly the scopes you have for a decision task.
Depends on: 1335915
Mentor: dustin
Keywords: good-first-bug
Priority: -- → P5
Component: Github → Services

I would like to work on this ! Some pointers to start would be really appreciated

Found in triage.

Dustin: is this handled now by parametrized roles?

Flags: needinfo?(dustin)

No, it's not, and it's still one of the things that makes implementing .taskcluster.yml pretty tricky. We should include this in thinking about ways to improve the GitHub experience /cc owlish.

Flags: needinfo?(dustin)
Blocks: github-bugs

Good reference material for GitHub rethink.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.