Maximum flexibility, as a plugin or built-in, in my view and without regards to feasibility, would be:

  • wait a configurable amount of time for the SIGTERM killed process to come to its natural completion (i.e. let it run its traps/handlers)
  • if not dead by the timeout, send SIGKILL and wait for process to be gone (N seconds, configurable)
  • If not dead, move on to the next job or hang (as determined by the user - sometimes hanging is the right thing: spectacular failures are usually easy to debug but it's a judgement call)
  • When moving on, perform the post-build steps

Regarding the last point, I am not sure whether Jenkins is supposed to perform the post-build steps when a build is killed by the user - but it is certainly something that would help me. Perhaps this is something that could be configured?

I do not know what would belong to a plugin vs. what should be built-in.

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/d/optout.

Reply via email to