Jobs just there sitting in the queue, since 1.610

[Vitor Machado]

Hi everyone,

Since version 1.610 exactly (and up to the most recent 1.613), when there's more than one job waiting in the queue, and they're blocked by the job currently running, they just sit there forever after the running job finishes.

It's as if Jenkins can't decide which job to run next from the queue and simply does nothing. It just says "Pending" and that's it. Master node shows no abnormalities. Jenkins console says nothing, just SUCCESS from the last running job.

Does anyone hae any idea what's going on?

My plug-ins are (all updated):

• Build Blocker
  
• Configuration Slicer
  
• Email-ext
  
• Green Balls
  
• HTML Publisher
  
• Mailer
  
• Matrix Authorization Strategy
  
• Naginator
  
• Simple Theme Plugin
  
• Startup Trigger
  
• TextFinder
  
• Wall Display Master Project
  

[Stephen Connolly]

I would suspect a race condition in this line: https://github.com/jenkinsci/build-blocker-plugin/blob/master/src/main/java/hudson/plugins/buildblocker/BlockingJobsMonitor.java#L83

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2c6c5118-a75b-4b79-b06e-00d88d676293%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Stephen Connolly]

https://github.com/jenkinsci/build-blocker-plugin/pull/5

[Vitor Machado]

So hopefully it should be fixed in the next build-blocker-plugin release? Awesome!

Thanks Stephen!

[Stephen Connolly]

I don't know if that is your issue. I do know that in 1.607 we changed was isBusy means so that it is accurate... and as a result you could get an NPE when evaluating. None of the other plugins look likely to be causing this issue, so it's something in Build Blocker is my #1 bet... just a question of what

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/783f8043-d09b-4c84-b3a1-64df11a77b9d%40googlegroups.com.

[Vitor Machado]

Well, I'm running 1.609 right now and have no problems. It's easily reproducible in 1.610, because it happens 100% of the time. So if this problem is indeed related to this 1.607 change, it's only showing itself on 1.610 and afterwards for me...

[Stephen Connolly]

1.610 added an extra sync to work around issues with Queue decision handlers

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d51bdca6-f284-418d-b538-21199842a96e%40googlegroups.com.