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

Job with status "pending description" do not start

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • None
    • Jenkins ver. 2.73.2 / Windows
      Parameterized trigger plug-in 2.35.2

      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.

          [JENKINS-47792] Job with status "pending description" do not start

          marlene cote added a comment -

          I have 2 downstream jobs from the same job, one of them runs and the other hangs with pending description. I just downgraded to 2.35.1 and upgraded multijob to 1.31 with no change in behavior. I did notice that if I kill the top job(upstream) the pending job runs.
          So, something in the upstream job is holding the downstream one in pending.

          marlene cote added a comment - I have 2 downstream jobs from the same job, one of them runs and the other hangs with pending description. I just downgraded to 2.35.1 and upgraded multijob to 1.31 with no change in behavior. I did notice that if I kill the top job(upstream) the pending job runs. So, something in the upstream job is holding the downstream one in pending.

          marlene cote added a comment -

          I have changed my upstream job to do a simple kick off another job instead of using phases and it is working. I need phases in the future though.. please??? thank you.

          marlene cote added a comment - I have changed my upstream job to do a simple kick off another job instead of using phases and it is working. I need phases in the future though.. please??? thank you.

          Jon Starbird added a comment -

          funeeldy so let me understand what you did, see if it works for me, you have  Mutli-Job that you just have it do a Trigger/Call Build On another Project and then it works?

           

          Jon Starbird added a comment - funeeldy so let me understand what you did, see if it works for me, you have  Mutli-Job that you just have it do a Trigger/Call Build On another Project and then it works?  

          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

          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

          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.

          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.

          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.

          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.

          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!

          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!

          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.

          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.

          Mikhail T added a comment - - edited

          "Me too". In this snapshot, the "Boost/Compile-32bit" and "Boost/Compile-64bit" both invoke (through parametrized trigger) the "Boost/Compile" with the Architecture-parameter set accordingly:

          Both of the jobs are in red, because they've been "running" for 13 hours. The two triggered instances of "Build/Compile" remain "in queue" and were never attempted during this time. Using the latest version of Jenkins (2.190.2 currently) and of all the plugins.

          Note, this is different from the problem I describe in JENKINS-60051 – where, with only two Executors available, the upper-level jobs remain "pending" themselves.

          Simply cancelling one of the builds does not unblock the other.

          Restarting Jenkins helps, however – a clear evidence of a bug

          Mikhail T added a comment - - edited "Me too". In this snapshot, the "Boost/Compile-32bit" and "Boost/Compile-64bit" both invoke (through parametrized trigger) the "Boost/Compile" with the Architecture -parameter set accordingly: Both of the jobs are in red, because they've been "running" for 13 hours. The two triggered instances of "Build/Compile" remain "in queue" and were never attempted during this time. Using the latest version of Jenkins (2.190.2 currently) and of all the plugins. Note, this is different from the problem I describe in JENKINS-60051 – where, with only two Executors available, the upper-level jobs remain "pending" themselves. Simply cancelling one of the builds does not unblock the other. Restarting Jenkins helps, however – a clear evidence of a bug

          Mikhail T added a comment -

          I downgraded the Parameterized Trigger plugin to 2.35.1 and now things seem to work:

          Note, that the blocked Compile-Foo builds are still each taking out an Executor – a problem described in JENKINS-60051 – but, at least, the triggered jobs seem to proceed.

          Mikhail T added a comment - I downgraded the Parameterized Trigger plugin to 2.35.1 and now things seem to work: Note, that the blocked Compile-Foo builds are still each taking out an Executor – a problem described in JENKINS-60051 – but, at least, the triggered jobs seem to proceed.

            huybrechts huybrechts
            fredericmeyrou Frédéric Meyrou
            Votes:
            10 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: