This message was deleted.

As an example: https://dev.azure.com/TerracottaCI/ehcache/_build/results?buildId=9975&view=logs&j=[…]-5b94-873e-ae483acce31c&t=bd32b9f3-1cb1-588e-44b9-5a0f46e80d0e

Try adding Maven Central before the plugin portal in your settings

pluginManagement

whoops… you mean this is a bad idea:

repositories {
  gradlePluginPortal()
  mavenCentral()
}

Yes, swap it around. And if you want to optimize it, exclude specific plugin markers and artifacts from maven central resolution

you could also not wipe out caches, there are a set of directories that are documented safe to be copied. https://docs.gradle.org/current/userguide/dependency_management.html#sub:cache_copy

yeah… just realized this is uglier than I expected - that existing reference (in the

build-logic

project) is there because I have explicit non-plugin dependencies. What’s the timeline on an infrastructure fix for this before I commit to also adding an entirely new repositories section to the top level

settings.gradle

?

you can use

content.(include|exclude)(Group|Module|Version)(ByRegex)?

in your repository definition to limit which artifacts Gradle will attempt to look up there