Last active
September 5, 2018 13:41
-
-
Save ahal/fdefbdfb3f122157d3a49cc0668c4efd to your computer and use it in GitHub Desktop.
Taskcluster views.json proposal
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"taskGroupId": "<taskGroupId>", | |
"views": [ | |
{ | |
"type": "subtask", | |
"tasks": ["<task id>", "<task id>", "..."], | |
"context": { | |
"description": "Linux64 opt Mochitest", | |
"symbol": "M", | |
"platform": "linux64/opt", | |
}, | |
}, | |
{ | |
"type": "subtask", | |
"tasks": ["<task id>", "<task id>", "..."], | |
"context": { | |
"description": "Windows10 64 opt Mochitest", | |
"symbol": "M", | |
"platform": "windows10-64/opt", | |
}, | |
}, | |
{ | |
"type": "taskcluster-unit", | |
"tasks": ["<task id>"], | |
"context": { | |
"description": "set allowed key (twice)", | |
"format": "tap", | |
"artifact": "report.tap", | |
}, | |
}, | |
{ | |
"type": "taskcluster-unit", | |
"tasks": ["<task id>"], | |
"context": { | |
"description": "set disallowed key", | |
"format": "tap", | |
"artifact": "report.tap", | |
}, | |
}, | |
], | |
} |
For the record I think a separate manifest (e.g views.json
) would be fine to have as a separate artifact. But using my earlier example in the first comment, treeherder could theoretically group all tasks that have the same "symbol" (and platform). In that case I don't think a separate artifact would be necessary.
I guess if there's additional metadata that only applies to the parent task, defining that in task-graph.json
would be clunky, and at that point a separate manifest/artifact might be better. But there's a chance the two problems we're trying to solve are different enough from one another that we're forcing round and square pegs into a triangular hole. (I do agree we should at least try to solve them both in a generic way)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the
taskcluster-unit
case, I would write out a file that specifies the results of running the tests soviews.json
would be self-referential really. Maybe putting it in the task definition would make the most sense in that case.