[JIRA] (JENKINS-47792) Job with in queue with status "pending description" do not start

145 views
Skip to first unread message

jstarbird@scisolutions.com (JIRA)

unread,
Jul 17, 2018, 2:30:02 PM7/17/18
to jenkinsc...@googlegroups.com
Jon Starbird commented on Bug JENKINS-47792
 
Re: Job with in queue with status "pending description" do not start

The workaround did not work for me. There is some other interaction here that is causing the issue. 

I get nothing in the logs for this. 

In my case I am running Jenkins 2.121.1 and it is getting into this Pending - Description  when launching a job from a Multi-Job. It happens every time, making multi-job worthless.

I am going to Clone this to the Multi-job plugin as well.

 

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

funeeldy@yahoo.com (JIRA)

unread,
Aug 3, 2018, 4:54:02 PM8/3/18
to jenkinsc...@googlegroups.com

I am also seeing this in the latest version and in 2.35.1. I have version 1.30 of multijob.
and version 2.12.1.1 of jenkins on windows.

jstarbird@scisolutions.com (JIRA)

unread,
Aug 3, 2018, 5:27:01 PM8/3/18
to jenkinsc...@googlegroups.com

This has gotten stranger for me. I also have this problem now by just using the Trigger/Call Builds on another project using Parameters.

The really strange part is I have other jobs that I use that same call in and they still work. I'm not sure what the issue is. I've tried removing all the params and it will still get stuck. 

 

funeeldy@yahoo.com (JIRA)

unread,
Aug 3, 2018, 5:30:02 PM8/3/18
to jenkinsc...@googlegroups.com

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.

funeeldy@yahoo.com (JIRA)

unread,
Aug 3, 2018, 5:42:02 PM8/3/18
to jenkinsc...@googlegroups.com

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.

jstarbird@scisolutions.com (JIRA)

unread,
Aug 3, 2018, 5:47:02 PM8/3/18
to jenkinsc...@googlegroups.com

marlene cote 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?

 

petr@prochazka.cc (JIRA)

unread,
Aug 29, 2018, 6:47:01 AM8/29/18
to jenkinsc...@googlegroups.com

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

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jstarbird@scisolutions.com (JIRA)

unread,
Sep 11, 2018, 2:15:02 PM9/11/18
to jenkinsc...@googlegroups.com

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.

jstarbird@scisolutions.com (JIRA)

unread,
Sep 11, 2018, 2:27:02 PM9/11/18
to jenkinsc...@googlegroups.com

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@keurig.com (JIRA)

unread,
Nov 12, 2018, 9:36:03 AM11/12/18
to jenkinsc...@googlegroups.com

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!

marlene.cote@keurig.com (JIRA)

unread,
Nov 12, 2018, 9:38:02 AM11/12/18
to jenkinsc...@googlegroups.com
marlene cote edited a comment on Bug JENKINS-47792
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.

marlene.cote@keurig.com (JIRA)

unread,
Nov 12, 2018, 9:47:02 AM11/12/18
to jenkinsc...@googlegroups.com
marlene cote edited a comment on Bug JENKINS-47792
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.guenther@kamg.de (JIRA)

unread,
Nov 19, 2018, 10:23:04 AM11/19/18
to jenkinsc...@googlegroups.com

Same here on one of my Jenkins instances. Updated this plugin to latest STABLE version and nothing is working anymore.

karsten.guenther@kamg.de (JIRA)

unread,
Nov 19, 2018, 10:36:02 AM11/19/18
to jenkinsc...@googlegroups.com
Karsten Günther edited a comment on Bug JENKINS-47792
Same here on one of my Jenkins instances. Updated this plugin to latest STABLE version and nothing is working anymore. Just downgraded it to 2.35.1 as proposed and everything is running again. Thanks to marlene. Obviously 2.35.2 is faulty and should not be marked as stable.

karsten.guenther@kamg.de (JIRA)

unread,
Nov 19, 2018, 11:46:01 AM11/19/18
to jenkinsc...@googlegroups.com
Karsten Günther edited a comment on Bug JENKINS-47792
Same here on one of my Jenkins instances. Updated this plugin to latest STABLE version and nothing is was working anymore. Just downgraded it to 2.35.1 as proposed and everything is running again. Thanks to marlene everyone . Obviously 2.35.2 is faulty and should not be marked as stable.

karsten.guenther@kamg.de (JIRA)

unread,
Nov 19, 2018, 11:47:05 AM11/19/18
to jenkinsc...@googlegroups.com
Karsten Günther edited a comment on Bug JENKINS-47792
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.

mi+jenkins-2019@aldan.algebra.com (JIRA)

unread,
Nov 5, 2019, 9:28:04 AM11/5/19
to jenkinsc...@googlegroups.com
Mikhail T updated an issue
 
Jenkins / Bug JENKINS-47792
Change By: Mikhail T
Attachment: image-2019-11-05-09-27-25-342.png
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

mi+jenkins-2019@aldan.algebra.com (JIRA)

unread,
Nov 5, 2019, 9:37:04 AM11/5/19
to jenkinsc...@googlegroups.com
Mikhail T updated an issue
Change By: Mikhail T
Attachment: image-2019-11-05-09-36-09-872.png

mi+jenkins-2019@aldan.algebra.com (JIRA)

unread,
Nov 5, 2019, 9:37:05 AM11/5/19
to jenkinsc...@googlegroups.com
Mikhail T commented on Bug JENKINS-47792
 
Re: Job with in queue with status "pending description" do not start

"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.

mi+jenkins-2019@aldan.algebra.com (JIRA)

unread,
Nov 5, 2019, 10:11:04 AM11/5/19
to jenkinsc...@googlegroups.com
Mikhail T edited a comment on Bug JENKINS-47792
"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:

!image-2019-11-05-09-36-09-872.png!


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.
!image-2019-11-05-09-27-25-342.png!


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 :(

mi+jenkins-2019@aldan.algebra.com (JIRA)

unread,
Nov 5, 2019, 10:30:03 AM11/5/19
to jenkinsc...@googlegroups.com
Mikhail T updated an issue
Change By: Mikhail T
Attachment: image-2019-11-05-10-29-51-699.png

mi+jenkins-2019@aldan.algebra.com (JIRA)

unread,
Nov 5, 2019, 10:32:02 AM11/5/19
to jenkinsc...@googlegroups.com
Mikhail T commented on Bug JENKINS-47792
 
Re: Job with in queue with status "pending description" do not start

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.

Reply all
Reply to author
Forward
0 new messages