Closed Bug 1335915 Opened 8 years ago Closed 6 years ago

[tc-github] Use json-e to parameterize .taskcluster.yml

Categories

(Taskcluster :: Services, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: owlish)

References

Details

Using json-e will make it a lot easier to produce exactly the desired task in .taskcluster.yml, without relying on data-munging by taskcluster-github. Basically, we can make the whole webhook payload available to json-e, and the user can access whatever fields they would like. We'll need some kind of gentle transition from the current templating schem -- maybe we just go from version 1 to version 2?
You have a link to "json-e"? Thank you!
Flags: needinfo?(dustin)
One feature that will be important here is a way to reduce redundancy -- .taskcluster.yml files tend to repeat the same task boilerplate over and over, and users will want to be able to write that once and then generate lots of tasks. I don't know what that would look like, but we can talk about ideas.
Blocks: 1372600
I've started twiddling around with this, after https://github.com/taskcluster/mozilla-taskcluster/pull/116
Assignee: nobody → dustin
This was deployed on Friday.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
oh, right, this is tc-github.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: Use json-e to parameterize .taskcluster.yml → [tc-github] Use json-e to parameterize .taskcluster.yml
Assignee: dustin → alesilva241
Assignee: alesilva241 → bugzeeeeee
Status: REOPENED → ASSIGNED
Blocks: 1252144
Blocks: 1389714
Blocks: 1332300
I think this is done, right Irene? A two-year-old-bug!
Flags: needinfo?(bugzeeeeee)
Yep, this is done!
Flags: needinfo?(bugzeeeeee)
Status: ASSIGNED → RESOLVED
Closed: 7 years ago6 years ago
Resolution: --- → FIXED
Component: Github → Services
You need to log in before you can comment on or make changes to this bug.