This message was deleted.
# community-support
s
This message was deleted.
v
Run all tasks
With your line you just run the
tasks
task which just lists all tasks, but does not execute them.
You only see problems of the tasks you actually executed.
If you can execute all tasks in your build, you could use
tasks --all
to list all tasks and then execute all tasks. But in many builds this might not work as there might be tasks that are not executable, or that do things like publishing and so on.
s
Yeah, exactly that's the problem. I wish there was something like s static analysis feature in Gradle to detect configuration cache issues in a task's code without actually running it... maybe one could even write a detekt rule for it.
p
How do you know if task uses
project
during execution, which isn’t compatible, without actually executing it?
s
Well, as mentioned, static code analysis should be able to tell.
p
Only for some use-cases with available sources.
v
It should be able to find some violations but pretty sure not every
s
Ok, anyway, I take that there's no way except manually running all tasks. Thanks!
👌 1
p
Otherwise prepare to get an award
😄 1