Record cause of interruption in DurableTaskStep

XMLWordPrintable

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Minor
    • Component/s: pipeline
    • None

      DurableTaskStep.Execution should set AbortException.cause to a FlowInterruptedException after successful stop. Would allow us to keep track of whether a particular sh step ended because a user aborted the build, or a timeout was exceeded, or because the process decided to exit on its own. catch blocks could process this information.

            Assignee:
            Jesse Glick
            Reporter:
            Jesse Glick
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: