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

Pipeline builds waits to resume infinitely

    XMLWordPrintable

Details

    Description

      Steps to reproduce the issue:

      1. Create a folder and create a pipeline job inside like this

      node ("ssh1") {
    stage('stage1') {
        echo "Hello stage1"
        sleep 60
    }
    stage('stage2') {
        echo "Hello stage2"
        sleep 60
    }
    stage('stage3') {
        echo "Hello stage3"
        sleep 60
    }
}

      2. Create a SSH slave and configure it to only accept builds from the folder previously created.
      3. Trigger the pipeline job and after that restart the Jenkins instance
      4. Check the build console log and you will get the issue

      Sleeping for 1 Min 0 Seg
Resuming build at Tue Jul 11 10:30:37 CEST 2017 after Jenkins restart
Waiting to resume part of FOLDER » test3 #1: ssh1 is offline
Waiting to resume part of FOLDER » test3 #1: ssh1 is offline
Waiting to resume part of FOLDER » test3 #1: ssh1 is offline
Waiting to resume part of FOLDER » test3 #1: ssh1 is offline
Waiting to resume part of FOLDER » test3 #1: ssh1 is offline
Waiting to resume part of FOLDER » test3 #1: ssh1 is offline
Waiting to resume part of FOLDER » test3 #1: ssh1 is offline
Waiting to resume part of FOLDER » test3 #1: ssh1 is offline
Waiting to resume part of FOLDER » test3 #1: Strict security prevents tasks without an owning item from executing.
Waiting to resume part of FOLDER » test3 #1: Strict security prevents tasks without an owning item from executing.
Waiting to resume part of FOLDER » test3 #1: Strict security prevents tasks without an owning item from executing.
Waiting to resume part of FOLDER » test3 #1: Strict security prevents tasks without an owning item from executing.
Waiting to resume part of FOLDER » test3 #1: Strict security prevents tasks without an owning item from executing.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-53837 Node steps are not correctly associated with their WorkflowRun through the Queue.Task API when restarting Pipelines

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          links to

          Web Link CloudBees Internal CD-182

          Activity

            People

              Unassigned Unassigned
              dariver Darío Villadiego
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: