Please do not cross-post to multiple Jenkins mailing lists; the users'
list was the correct place for this question.
On 17/03/15 23:50, Kishore RP wrote:
Hello community,
We use a multi config job to trigger jobs on multiple slaves
When we trigger jobs on multiple slaves, during one of the subjob, if
one of the slaves goes offline due to some system issue, the other
slaves are starved and the other jobs do not progress at all, how do we
auto abort above kind of build?
The slaves are launched using jnlp mechanism, build time out plugin
doesnt seem to work when the executor starvation occurs.
Any suggestions would be more than welcome.
Regards
Kishore
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/55092619.7090805%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.
