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

Node steps are not correctly associated with their WorkflowRun through the Queue.Task API when restarting Pipelines

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      workflow-durable-task-step 2.24

      Description

      When a pipeline resumes inside of a node block, the task that gets queued in Jenkins to restart the build is an ExecutorStepExecution.PlaceholderTask. When a custom QueueTaskDispatcher is in use, the Queue.BuildableItem passed to methods such as canTake will be an instance of ExecutorStepExecution.PlaceholderTask. However, calling getOwnerTask on the item does not return the WorkflowJob for the Pipeline and instead returns the ExecutorStepExecution.PlaceholderTask instance here, which means that some custom QueueTaskDispatcher instances may not be able to correctly dispatch Pipeline jobs after they are restarted.

        Attachments

          Issue Links

            Activity

            Hide
            dnusbaum Devin Nusbaum added a comment -

            Fixed in workflow-durable-task-step 2.24.

            Show
            dnusbaum Devin Nusbaum added a comment - Fixed in workflow-durable-task-step 2.24.

              People

              • Assignee:
                dnusbaum Devin Nusbaum
                Reporter:
                dnusbaum Devin Nusbaum
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: