From 004a2cb5a6080f14408aaa8f7f429daa8565269e Mon Sep 17 00:00:00 2001 From: Renat Akhmerov Date: Fri, 8 Mar 2019 21:21:34 +0700 Subject: [PATCH] Release note for the "execution-get-report" command Change-Id: Ie6e00ca4fb77875bc7d10a09d9b5c929365bd67b --- ...xecution_get_report_command-b91b0a0db71716cd.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 releasenotes/notes/add_execution_get_report_command-b91b0a0db71716cd.yaml diff --git a/releasenotes/notes/add_execution_get_report_command-b91b0a0db71716cd.yaml b/releasenotes/notes/add_execution_get_report_command-b91b0a0db71716cd.yaml new file mode 100644 index 00000000..4cb7f862 --- /dev/null +++ b/releasenotes/notes/add_execution_get_report_command-b91b0a0db71716cd.yaml @@ -0,0 +1,12 @@ +--- +features: + - | + Added the new CLI command "execution-get-report" that prints information + about the entire workflow execution tree, including its task executions, + action executions and nested workflow executions. The command currently + has filters "--errors-only" that allows to find only ERROR paths of the + execution tree (enabled by default), "--no-errors-only" that allows to + print all tree regardless of the elements' state, "--max-depth" that + allows to limit the depth of the tree that needs to be printed. + This command should be especially useful for debugging failure situations + when it's not easy to manually track down to the root cause.