![]() |
|
|
|
|
|
|
Change By:
|
Jesse Glick
(21/Jan/15 12:46 PM)
|
|
Issue Type:
|
Bug
New Feature
|
|
Description:
|
Some of our test-suite items can occasionally deadlock, causing a build to never finish. The
[
Build Timeout Plugin
(
|
http://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin
)
]
supports failing a job when nothing happens (i.e. no log output) for a sufficient length of time. It would be good to get this behaviour in Workflow.
|
|
Labels:
|
api
|
|
Assignee:
|
Jesse Glick
Kohsuke Kawaguchi
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
Would be useful in some cases. I am not sure how difficult this would be. BuildTimeoutWrapper uses BuildWrapper.decorateLogger for this purpose, which is too low-level (assumes access to an OutputStream for the whole build) and so is not available in a workflow (cf. JENKINS-24673). There would have to be something like a TaskListenerDecorator which could be passed into BodyInvoker.withContext and interpreted by LogActionImpl, perhaps.
By the way for the use case originally reported here, it is arguably better to just impose a per-suite timeout in the test framework or test runner, such as in Surefire.