Race condition in FlowExecutionList

XMLWordPrintable

      Hi,

      We found a potential bug that can only be replicated in pipeline jobs. Essentially when a job a running and a Jenkins restart occurs, the job is left hanging infinitely:

      Resuming build at Tue Jan 03 10:37:18 UTC 2017 after Jenkins restart
Waiting to resume part of TestRun2 #2: Waiting for next available executor
Waiting to resume part of TestRun2 #2: Waiting for next available executor
Waiting to resume part of TestRun2 #2: Waiting for next available executor
Waiting to resume part of TestRun2 #2: Waiting for next available executor
Waiting to resume part of TestRun2 #2: Waiting for next available executor
Waiting to resume part of TestRun2 #2: Waiting for next available executor
Waiting to resume part of TestRun2 #2: Waiting for next available executor
...

      I noticed that this behaviour does not exhibit on any other job types. i.e. freestyle.

      Here is a simple test pipeline script:

      node('XXXXX') {

  stage 'Stage 1'
    println 'Deploying to Stage 1...'

  stage 'Stage 2'
    println 'Running Tests in Stage 2'
    sleep 120
    println 'Tests passed!'

  stage 'Stage 3'
    println 'Deploying to Stage 3...'

}

      ...Restart Jenkins as soon as it enters Stage 2, to replicate such behaviour.

      Currently I am using version 2.3, but I believe this issue was replicated in previous versions.

      Please can you help me explain why this behaviour only exists in pipeline jobs?

      Kind Regards,
      Tuan

            Assignee:
            Jesse Glick
            Reporter:
            Tuan Nguyen
            Votes:
            3 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: