You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FWIW I'm willing to open a PR to provide this, more so looking for alignment that the team would accept something like this
We don't want to break anyone depending on the existing environment variable configuration. Introducing a second source for this does raise a question of which one should take precedent when both are present - if there's a norm for this within the project that would be helpful to hear (also poking around for a few examples)
Teams working in tighter security environments may have network traffic to external maven repositories blocked
This has a few negative impacts
Gradle isn't able to download Groovy resources that it needs/wants
Erodes developer productivity, during IDE sync we see ~1700 retries fail while attempting to fetch these which can add upwards of ~4 minutes to our IDE sync times
As mentioned in #24217 these is an existing workaround that resolve this issue
This is great for an individual but hard for teams. In an environment of hundreds or thousands of engineers we'd have to make a large announcement, hope they apply the workaround, etc. This is pretty expensive and results aren't very durable for new people joining a team, machine upgrades, etc
The text was updated successfully, but these errors were encountered:
This feature request is in the backlog of the relevant team, but this area of Gradle is currently not a focus one, so it might take a while before it gets implemented.
Opening a PR for this would be appreciated, thanks! See CONTRIBUTING.md for more information.
As for your question about priority, see Build Environment documentation: environment variables have the lowest precedence.
Also, some corporate artifactory/repository URLs require authentication. It would be great if the solution also supported providing a standard maven repo for downloading the libs
Expected Behavior
Provide a Gradle property that would allow an override for the Gradle library repository that can be committed to gradle.properties
FWIW I'm willing to open a PR to provide this, more so looking for alignment that the team would accept something like this
We don't want to break anyone depending on the existing environment variable configuration. Introducing a second source for this does raise a question of which one should take precedent when both are present - if there's a norm for this within the project that would be helpful to hear (also poking around for a few examples)
Current Behavior (optional)
Context
Teams working in tighter security environments may have network traffic to external maven repositories blocked
This has a few negative impacts
As mentioned in #24217 these is an existing workaround that resolve this issue
This is great for an individual but hard for teams. In an environment of hundreds or thousands of engineers we'd have to make a large announcement, hope they apply the workaround, etc. This is pretty expensive and results aren't very durable for new people joining a team, machine upgrades, etc
The text was updated successfully, but these errors were encountered: