[GRADLE-2345] Repositories that do not respond (i.e. timeout) are problemetic Created: 11/Jun/12 Updated: 17/Nov/16 Resolved: 17/Nov/16
The linked to forum post points out that Gradle will try over and over (for each new dependency) to contact a non responsive repository.
We might be able to do something here such as allow the tuning of the timeouts or fail the resolve on a timeout.
|Comment by Dave Smith [ 15/May/14 ]|
We have the same problem, in our case because one of our artifact repositories is behind a private firewall. When developers are off-site and forget (or are unable) to connect to the VPN, a Gradle build will hang for 3-5 minutes before failing to refresh the dependencies. The result is a "java.net.ConnectException: Operation timed out" after a 75 second wait for the offline server to respond; multiply over a few retries and the process takes a significant amount of time.
A way to control this, or a much lower default for the socket connect timeout would be much appreciated.
|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 Danny Thomas [ 15/Nov/16 ]|
|Comment by Eric Wendelin [ 17/Nov/16 ]|