[
https://issues.jenkins-ci.org/browse/JENKINS-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160227#comment-160227
]
Chris Nogradi commented on JENKINS-12994:
-----------------------------------------
I tried upgrading to 1.452 and 1.455 and both behave as described above with
all jobs remaining in 'Waiting for next executor' state with all nodes free.
Downgrading to 1.451 restores functionality.
> Quiet period is blocking other jobs in queue
> --------------------------------------------
>
> Key: JENKINS-12994
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12994
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Platform: All, OS: All
> Reporter: teetoivo
>
> Starting from version 1.452, a job in queue waiting for the quiet period to
> pass is blocking all other jobs that have been queued after it.
> Example:
> # Job A has quiet period set to 10 seconds
> # Job B has quiet period set to 300 seconds
> # Job C has quiet period set to 100 seconds
> # Jobs get queued in A-B-C order.
> # Job A starts executing after 10 seconds
> # After 100 seconds, status of job C changes to "pending - Waiting for next
> available executor" even if free executors are available
> # After 300 seconds both jobs B and C start executing
> This problem is hardly visible when short quiet periods are used but becomes
> problematic with longer quiet periods or plugins like Naginator that will
> increase the quiet period to hours if the builds fail enough.
> Version 1.451 is the last release where this problem isn't visible. From
> public releases, at least 1.452 and 1.454 are affected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
