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.

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:

• Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
• Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Created https://github.com/gradle/gradle/issues/868

Moved to https://github.com/gradle/gradle/issues/868