Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-52149

wfapi shows incorrect status of failed/aborted job when job does not propagate or is in a try-finally block

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: workflow-api-plugin
    • Labels:
      None
    • Environment:
      Jenkins ver 2.107.2
      Windows Server 2016
    • Similar Issues:

      Description

      Within a pipeline and within a stage, if I launch a job and it fails, the status of the job will be FAILED. 

      If I use the wfapi from the pipeline, I can get the status of all stageFlowNodes for that stage. The stageFlowNode for the job that failed will be FAILED.
      However, if I launch the job and set propagate to false, the job will fail, but the stageFlowNode for that job will be SUCCESS.

      Similarly, if I launch the job with propagate true, but I launch the job within a try-catch-finally block, the stageFlowNode for that job will be SUCCESS.
      As a result, I am unable to accurately get the status of a failed stageFlowNode when it either doesn't propagate or is within a try-catch-finally block.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              klamb Ken Lamb
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: