The wrapper script should honor http(s)_proxy variables

[sschuberth]

Expected Behavior

Running gradlew on a (Linux / Mac) system that has the http_proxy and / or https_proxy environment variables set should be able to download the configured Gradle distribution though the specified proxy.

Current Behavior

The gradlew script does not pass any proxy configuration from the http_proxy / https_proxy environment variables to the JVM that runs the Java implementation for the wrapper, resulting in the download of the Gradle distribution to fail on systems that can only access the Internet via a proxy.

Context

In environments behind a corporate proxy running a Gradle project's ./gradlew fails out of the box because the JVM does not know about the proxy even if http_proxy / https_proxy is set. A Gradle user has to manually pass the http(s).proxy* JVM system properties either directly to gradlew on the command line via -D, or configure them in the ~/.gradle/gradle.properties file.

This is inconvenient extra work and not in line with other package managers / build systems like e.g. Yarn which do respect http_proxy / https_proxy.

As such it would be nice if the gradlew script would by default parse http_proxy / https_proxy and pass the information on via the http(s).proxy* system properties to the JVM that runs the Java implementation for the wrapper.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[stale]

This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request.

[augi]

IMHO still valid.

[gnaggnoyil]

@sschuberth I saw you once committed code that honor http(s)_proxy env vars in PR #12598, but later force pushed and removed those code. Do you still think it's a good idea to honor environment variables?

[sschuberth]

Yes, I still think honoring the http(s)_proxy environment variables is a good idea. I just didn't want to do too many things at a time and keep the amount of changes to a minimum in that PR. And after my PR I didn't really need that feature anymore as I could use Gradle properties instead; honoring the environment variables would have just been convenience.

[HackToday]

if environment proxy variables be honored would be better, right now, seems need pass to program like -Dhttp.proxyHost etc.

[jbartok]

Thank you for your interest in Gradle!

This feature request is in the backlog of the relevant team, but this area of Gradle is currently not in focus. It might take a while before it gets implemented.