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

Job with in queue with status "pending description" do not start

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Blocker
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Jenkins ver. 2.73.2 / Windows
      Parameterized trigger plug-in 2.35.2
    • Similar Issues:

      Description

      Called Job by the parameterized options do not start after migration from Jenkins ver. 2.60.2 to Jenkins ver. 2.73.2 with all plugins updates.

      The Job is stuck with executor status "pending description" and has no console logs.

      When started alone with parameters the target Jobs works fine.

      With V2.35.2 fail when V2.35.1 works well, so there is a regression in hte last published version that leads to this situation.

        Attachments

          Activity

          Hide
          petrp Petr Prochazka added a comment -

          It looks like that somebody should fix this issue or remove wrong version from repository:

          https://updates.jenkins-ci.org/download/plugins/parameterized-trigger/2.35.2/parameterized-trigger.hpi

          Show
          petrp Petr Prochazka added a comment - It looks like that somebody should fix this issue or remove wrong version from repository: https://updates.jenkins-ci.org/download/plugins/parameterized-trigger/2.35.2/parameterized-trigger.hpi
          Hide
          jstarbird Jon Starbird added a comment -

          I'm still having this issue. It does only seem to impact new jobs as I do have other jobs that have not been edited in long time that still work. 

          I am currently up to Jenkins 2.121.3.

          Also, I had not noticed this before but in the Job queue if I hover over the pending job it says Upstream project of Full Build is already building.  That seems like it's not executing because it's waiting for it's parent job to finish.

          I do not have anything set for any job to wait for upstream jobs. The parent job is set to wait for the downstream job to finish before it continues.

          Show
          jstarbird Jon Starbird added a comment - I'm still having this issue. It does only seem to impact new jobs as I do have other jobs that have not been edited in long time that still work.  I am currently up to Jenkins 2.121.3. Also, I had not noticed this before but in the Job queue if I hover over the pending job it says Upstream project of Full Build is already building.  That seems like it's not executing because it's waiting for it's parent job to finish. I do not have anything set for any job to wait for upstream jobs. The parent job is set to wait for the downstream job to finish before it continues.
          Hide
          jstarbird Jon Starbird added a comment -

          Ok. I seemed to have fixed my issue. 

          I went into the parent job and enabled the block until upstream and downstream,  saved. Reopened and disabled them. 

          Then opened each job it was calling and then all of them showed they were being blocked while upstream job was building. I then disabled that flag on all of those jobs and then the build would run properly.

          It appears that somehow the block upstream flag is set but not shown to be set for the downstream jobs or something along those lines.

          Show
          jstarbird Jon Starbird added a comment - Ok. I seemed to have fixed my issue.  I went into the parent job and enabled the block until upstream and downstream,  saved. Reopened and disabled them.  Then opened each job it was calling and then all of them showed they were being blocked while upstream job was building. I then disabled that flag on all of those jobs and then the build would run properly. It appears that somehow the block upstream flag is set but not shown to be set for the downstream jobs or something along those lines.
          Hide
          mcote55 marlene cote added a comment - - edited

          I upgraded jenkins and all plugins this weekend for my regular maintenance, having forgotten about this problem.  So, I am seeing it again!

          I am at jenkins version 2.138.3.

          I tried what Jon suggested above with no luck.

            We really need a fix for this.  I am happy to gather dumps or whatever you need to get this fixed!

          I also tried aborting the upstream job and then the downstream one runs.

          just downgraded the plugin to 2.35.1 and everything is working again. thank goodness!

          Show
          mcote55 marlene cote added a comment - - edited I upgraded jenkins and all plugins this weekend for my regular maintenance, having forgotten about this problem.  So, I am seeing it again! I am at jenkins version 2.138.3. I tried what Jon suggested above with no luck.   We really need a fix for this.  I am happy to gather dumps or whatever you need to get this fixed! I also tried aborting the upstream job and then the downstream one runs. just downgraded the plugin to 2.35.1 and everything is working again. thank goodness!
          Hide
          xxthunder Karsten Günther added a comment - - edited

          Same here on one of my Jenkins instances (Windows 2012R2). Updated this plugin to latest STABLE version and nothing was working anymore. Just downgraded it to 2.35.1 as proposed and everything is running again. Thanks to everyone. Obviously 2.35.2 is faulty and should not be marked as stable.

          Show
          xxthunder Karsten Günther added a comment - - edited Same here on one of my Jenkins instances (Windows 2012R2). Updated this plugin to latest STABLE version and nothing was working anymore. Just downgraded it to 2.35.1 as proposed and everything is running again. Thanks to everyone. Obviously 2.35.2 is faulty and should not be marked as stable.

            People

            • Assignee:
              huybrechts huybrechts
              Reporter:
              fredericmeyrou Frédéric Meyrou
            • Votes:
              9 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

              • Created:
                Updated: