[
https://issues.jenkins-ci.org/browse/JENKINS-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161392#comment-161392
]
johno edited comment on JENKINS-13373 at 4/9/12 9:21 PM:
---------------------------------------------------------
This can be reproduced by configuring three jobs, two jobs job-A and job-B
which are chained, job-B has a quiet period, and an independent job job-C, when
job-A completes and job-B is in its quiet period, job-C won't start (even
though executors are available) until job a quiet period is over.
was (Author: johno):
Basically there are a few independent jobs, job a completes, goes into
quiet period, job b is triggered, and won't start (even though executors are
available) until job a quiet period is over.
> Job in quiet period blocks other jobs even if executors are available
> ---------------------------------------------------------------------
>
> Key: JENKINS-13373
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13373
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Reporter: johno
> Attachments: queue.png
>
>
> If there is a job in quiet period other jobs which do not depend on its
> completion will block even if executors are available.
--
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
