-
Suggestion
-
Resolution: Timed out
-
None
-
0
-
I'd like to see a feature that lets us know through a log file (and perhaps other configurable ways) that a child plan was triggered, or not triggered.
In the case of not being triggered, explain why.
For example:
Setup 'planA' with a dependency to 'planB'.
planA has 3 branches: master (default), foo, and bar.
planB only has 1 branch: master (default)
The 'foo' branch in planA is triggered.
Even though planA is configured to trigger child planB when it completes successfully, it won't because planB doesn't have the same branch.
Of course, this is documented, but the interface doesn't lend itself to understanding the chain of events if a problem occurs. This leads to difficult to diagnose situations that is more guess work than definitive logging output.
I'd like to see an option that allows us to get better information about these chains of plans.
Add more logging information to a parent plan when a child plan does/doesn't execute.
-
Suggestion
-
Resolution: Timed out
-
None
-
0
-
I'd like to see a feature that lets us know through a log file (and perhaps other configurable ways) that a child plan was triggered, or not triggered.
In the case of not being triggered, explain why.
For example:
Setup 'planA' with a dependency to 'planB'.
planA has 3 branches: master (default), foo, and bar.
planB only has 1 branch: master (default)
The 'foo' branch in planA is triggered.
Even though planA is configured to trigger child planB when it completes successfully, it won't because planB doesn't have the same branch.
Of course, this is documented, but the interface doesn't lend itself to understanding the chain of events if a problem occurs. This leads to difficult to diagnose situations that is more guess work than definitive logging output.
I'd like to see an option that allows us to get better information about these chains of plans.