1433471 - better output from trigger_action.py

Status: RESOLVED INCOMPLETE

(Release Engineering :: Release Automation, enhancement, P1)

Description

[[e-mail] (:bhearsum)]

Currently, trigger_action.py spits out the task definition of the Task it will trigger. Most of this information is not useful to humans. We should print out the useful parts in a more readable way, such as:
* taskId of the task
* taskGroupId of the graph it will generate, ideally with a link to the inspector
* action flavor (even though this is part of the input, it's nice to see it as confirmation)
* Some information pulled from the task ids used as input. Eg: their shipping product/phase (if applicable). Basically - something that helps a user confirm that they've actually used the taskIds they should've.

Comment 1

[Aki Sasaki (not active)]

+1 :) I bet the current output is great for debugging while writing the code, but I pretty much gloss over it while using it.

Comment 2

[Jordan Lund (:jlund)]

We no longer manually run trigger_action.py during releases. Instead, ship-it takes care of all graph generations.

@rail - do we use trigger_action.py in ship-it? If so, would its output benefit from this bug?

from a glance, it looks like we don't

Could we close this if not relevant anymore?

Comment 3

[Rail Aliiev [:rail]]

I think the only use case for trigger_action.py is triggering partner repacks now. I think we can close this bug in favour of bug 1530859.