jamesfredley opened a new pull request, #16566:
URL: https://github.com/apache/grails-core/pull/16566

   ## Problem
   
   On `7.0.x`, dependency resolution never declared Maven Central. The only 
release repository was `https://repo.grails.org/grails/restricted`, so every 
release lookup went through that Cloudflare host. CI also set both 
`cacheDynamicVersionsFor` and `cacheChangingModulesFor` to 0 hours, which 
re-lists dynamic release versions on every job.
   
   Fixed versions are immutable. Gradle does not need to re-poll them. 
Snapshots do need to be polled quickly.
   
   This is the repository-pressure part of #16544. It does not implement the 
rest of that issue.
   
   ## Fix
   
   - Resolve releases from Maven Central first, with `releasesOnly()`.
   - Request `org.gradle:gradle-tooling-api` only from 
`https://repo.gradle.org/gradle/libs-releases`. 8.14.5 is not on Central.
   - Resolve plugin libraries that are not on Central from the Plugin Portal, 
also `releasesOnly()`. `buildSrc` consumes several of those as ordinary 
dependencies.
   - Remove the unfiltered `repo.grails.org` fallback.
   - Keep the existing snapshot and staging content filters.
   - Poll changing modules immediately on ordinary CI, within 10 minutes 
locally, and not at all during a reproducible build. Dynamic release listings 
stay at Gradle's 24 hour default. `SOURCE_DATE_EPOCH` wins over `CI`.
   - Move the CI `modules-2` cache key to `gradle-deps-v2`, including the 
restore prefix, so metadata that was sticky to `repo.grails.org` is not 
restored.
   
   ## Verification
   
   - Cold `:grails-shell-cli:compileGroovy` and `:grails-core:compileGroovy` 
succeeded against a fresh Gradle user home.
   - `:build-logic:test --tests 
org.apache.grails.buildsrc.DependencyCachePolicySpec --tests 
org.apache.grails.buildsrc.GrailsRepoSettingsPluginSpec` passed.
   - Root `help` configured successfully with the shared cache policy on the 
buildscript classpath.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to