[GRADLE-1393] Add a timeout as a generic feature of a task. Created: 21/Feb/11 Updated: 20/Jan/17 Resolved: 04/Jan/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 0.9.2 |
Fix Version/s: | None |
Type: | New Feature | ||
Reporter: | Hans Dockter | Assignee: | Unassigned |
Resolution: | Duplicate | Votes: | 5 |
Description |
I have seen a couple of times the situation where the build had to call fragile custom code that now and then get stuck. For such tasks being able to set a timeout that let the build fail would be very helpful. BTW: Another feature that is only offered on CI so far but belongs to the build IMO. |
Comments |
Comment by William Lichtenberger [ 04/Jan/13 ] |
It would be nice to put a time out feature on a generic task itself. We're experimenting with using gradle to run system tests and they can hang indefinitely... we could always just use Ant's timeout feature... but I'd prefer for gradle to have something. |
Comment by Benjamin Muschko [ 15/Nov/16 ] |
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
Comment by Sundar Jayaraman [ 30/Dec/16 ] |
Is there a follow up issue created in github? I have been trying to find a way to implement timeouts during execution rather than using junit timeouts inside test classes. I still haven't figured how to do it. |
Comment by Benjamin Muschko [ 30/Dec/16 ] |
@Sunar So far there's no issue for it yet. Would you mind helping us out by creating it? |
Comment by Sundar Jayaraman [ 04/Jan/17 ] |
Comment by Benjamin Muschko [ 04/Jan/17 ] |
Thanks for creating the issue on GitHub. |
Comment by Sundar Jayaraman [ 20/Jan/17 ] |
@William Can you help with the workaround for this issue, till it gets addressed? I haven't been able to figure it out myself yet. Thanks!! |