[ https://issues.jenkins-ci.org/browse/JENKINS-9688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163422#comment-163422 ]
Jose Sa commented on JENKINS-9688: ---------------------------------- Even with delays it got stuck (maybe because I used exact same quiet period). Now I've configured different quiet periods to avoid this. > Build runs on master without executor and get stuck > --------------------------------------------------- > > Key: JENKINS-9688 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9688 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Reporter: protocol7b > Attachments: job_time_null.png > > > In the ASF Jenkins, we do not allow builds to run on master. Thus, we have > set the number of executors on master to zero. Even so, one build recently > (https://builds.apache.org/hudson/job/Axis2/774/) got assigned to run on > master. The build is configured with a label to run on one of the slaves, but > somehow Jenkins assigned it incorrectly. > Running on master also meant it got stuck, presumably due to the lack of > executors, without any way of stopping it. -- 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