[
https://issues.jenkins-ci.org/browse/JENKINS-9688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jose Sa updated JENKINS-9688:
-----------------------------
Attachment: job_time_null.png
The problem still occurs in 1.458 see:
!job_time_null.png!
We have multiple jobs using the same lock representing a test environment, but
without any quiet period. These jobs are not meant to run on master, but on a
build slave, but in the build status it shows:
"Started 1 day 14 hr ago
Build is being executed for null on master"
Maybe activating the default quiet period (30 seconds) will help in this
situation.
> 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
