1213283 - Add display only "summary" option to |mach taskcluster-graph|

Status: RESOLVED FIXED

(Taskcluster :: General, defect)

Description

[Andrew Halberstadt [:ahal]]

It would be handy to have a command line option that only displays a human readable summary of the graph for debugging purposes. As it stands, you have to sift through a massive json structure or grep the magic builder names to see if the graph contains the proper jobs.

Comment 1

[Andrew Halberstadt [:ahal]]

Attachment: MozReview Request: Bug 1213283 - Add option to only print task names in |mach taskcluster-graph|, r=dustin

Bug 1213283 - Add option to only print task names in |mach taskcluster-graph|, r=dustin

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

Comment on attachment 8671946 [details]
MozReview Request: Bug 1213283 - Add option to only print task names in |mach taskcluster-graph|, r=dustin

https://reviewboard.mozilla.org/r/21657/#review19465

Too cool - thanks!

I wonder if there's a way to have the decision task also print this out, separately from outputting the graph..

Comment 3

[Andrew Halberstadt [:ahal]]

Yeah, that would be useful! We could add some kind of --output-file argument where if specified, the graph is saved there instead of stdout. Then the human readable version can go to stdout instead.

Sort of related.. I'm not entirely sure why 'taskcluster-graph' is a mach command in the first place, as opposed to a module that gets called directly by the decision (without going through mach). We could still keep the mach command around for local debugging, but wouldn't have to worry about breaking things in automation.

I'll land this patch for now and file a follow up to tackle the rest.

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

Yeah, there's been some discussion of rewriting the graph generation to be in JS (still in-tree, but not part of mach).

That would make it easier to do things like make TC API calls (so adding the graph directly, rather than spitting JSON to an artifact and relying on the worker) and also give a nice JSON-y language to use for templating.

It's still a rather vague idea.

Comment 5

[Pulsebot]

https://hg.mozilla.org/integration/mozilla-inbound/rev/bac359fbd7f5

Comment 6

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/bac359fbd7f5