[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger

[theta...@java.net (JIRA)]

thetaphi commented on JENKINS-17566 Severe polling error when using script trigger One detail about this configuration: At the time of the polling, the slave node is not yet running (it is a VirtualBox VM started only when jobs are running), so when scripttrigger triggers the build, the job should be queued and the slave node starts up because of this triggering. Maybe this is the reason for the "Can't find eligible nodes" error. But scripttrigger is configured to run on node with label "master", so the child should not be involved. The shell script behind script trigger is just a check ("pgrep ..."), if other VirtualBox VMs are running at the same time, so scripttrigger will not trigger the job, if another VM is running concurrently (because too many VMs cannot be handled by the server it is running on). The whole setup works sometimes, but in most cases you have to trigger the job manually.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.