--include-build + com.gradle.enterprise fails with strange error message
#22521
Comments
TWiStErRob
changed the title
--include-build fails with strange error message--include-build + com.gradle.enterprise fails with strange error message
|
Thank you for providing a valid reproducer. The issue is in the backlog of the relevant team but the existence of a workaround makes it non-critical so it might take a while before a fix is made. In the reproducer there's a cycle in included builds between Keeping that cycle and removing the Gradle enterprise plugin also makes the reproducer work. It seems this is the combination of these two things that ends up failing the build. |
eskatos
added
has:reproducer
|
@eskatos I would We recently noticed that it's not only the enterprise plugin, changing plugins {
- id("com.gradle.enterprise") version "3.11.2"
+ id("com.gradle.common-custom-user-data-gradle-plugin") version "1.8.2"
}which suggests any plugin would make this fail. I wouldn't say that it has a workaround, because the workaround is non-viable in real life: we want to use the plugins. Removing any line in the reproducer makes it work, yes, but that's just because the reproducer is truly minimal. Each of the lines are meaningful, solve a problem in production code, therefore they're required for the build to be correct, so we cannot consider them as workarounds. |
|
I still think we have a reproducer. It even reproduces back to Gradle 5.0. The workaround is to remove the cycle in included builds. Isn't it applicable to your real use case? |
Eh, I was trying to pick a random plugin, but don't know many plugins that apply to settings.
Huh, yes, that seems to be a lucky solution, I just didn't see the conversation by others. Thanks for your help and patience, Paul! |
Sorry about the title, can't be more specific as I don't understand what's going on.
Expected Behavior
"Just works" as documented.
Current Behavior
Full log with stack trace
Context
@VitalyVPinchuk was trying to do the following: run detekt (from source) on projects without changing their code in any way.
--include-buildlooks like a good candidate for this and while experimenting he ran into this issue; I just created a minimal repro.Original (way too complex) repro:
android-components$ gradlew --include-build ../detektSteps to Reproduce
including$ gradlewto validateincludingproject works on its ownincluded$ gradlewto validateincludedproject works on its ownincluding$ gradlew --include-build ../included --no-daemonto get the errorYour Environment
Build scan URL: N/A fails to apply plugins in settings.gradle
Gradle: 7.5.1
Workaround
Remove enterprise plugin.
The text was updated successfully, but these errors were encountered: