https://gradle.com/ logo
Join Slack
Powered by
This message was deleted.
# community-support
s
This message was deleted.
l
Hi @Daan - build scans can tell you this …
The above is from 
performance/configuration
…
That’s the inspector, accessible via this blue icon:
Created immediately
means that the task was not created lazily.
Created during configuration
these are the tasks that were realized during this script/plugin (i.e. what you are looking for). It’s not where they are registered, but where they are created/realized.
d
I'm aware that normally the build scan shows you this information, but the issue is that no script/plugin shows that it created/realized any task yet I'm seeing that tasks are created during configuration. In the second red block, there is no "x tasks created".
v
Add a configuration action to all tasks and set a breakpoint within?
🤔 1
d
(Tried it with the Gradle Enterprise plugin 3.10 and Gradle Enterprise 2022.2)
Thanks again @Vampire, that of course works, didn't think of it
Copy code
allprojects {
    tasks.configureEach {
        println "${it.project.path}:${it.name} configured"
    }
}
👌 1
l
@Daan when you say second block, you mean the one with (2) right? I see 
94 tasks created
and 
519 tasks created
there. I’m not quite sure what you are referring to with “no script/plugin shows that it created/realized any task”.
d
That screenshot is from the docs, this is what I'm seeing (cannot really share more :/)
l
Not sure what’s going on here then. If you’re able, please share the nature of where these things are being resolved as it may be case we don’t handle.
d
@Luke Daley I found an issue which seems to be exactly what I was running into, https://github.com/gradle/gradle/issues/19498. Not sure if this can or should be caught in the build scan.
3 Views
Open in Slack
PreviousNext
Powered by