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

Triggering the same job twice results in zombie workflow run


    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • pipeline
    • None
    • Jenkins ver. 1.610
      workflow-plugin 1.5

      When two workflow jobs try to trigger the same job at the same time, java.hudson.model.Queue#scheduleInternal may detect a duplicate.

      When that happens, a second instance of WaitingItem does not get created, meaning one of the workflow runs will have no listeners related to the triggered job.

      When the triggered job ends, only one workflow run will be notified and continue, the other one will stay listening forever.

      The workaround I've had to apply to deal with this is running the following in scriptler:




      {it.context.onFailure(new Exception())}


            jglick Jesse Glick
            micpiekar Michal Piekarczyk
            0 Vote for this issue
            3 Start watching this issue