On 15/07/2015 18:07, Jeff Dickerson wrote:
The only way to recover from this, is to restart the Jenkins service
on the master.
Well depending what that thread is you could kill it in the script console.
(Killing threads is considered 7/10 on my evil scale)
I really don't like the idea that one rogue job can bring down the
entire system.
It doesn't sound like it is the job that is the problem but a plugin.
A search for a imilar ticket in the issue tracker
(issues.jenkins-ci.org) and if non present a new ticket against the
plugin may help.
I just wanted to check that you're also not running the build on the
master are you - you are using slaves?
/James
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/55A6D281.3020707%40teilo.net.
For more options, visit https://groups.google.com/d/optout.
