This message was deleted.
# community-support
s
This message was deleted.
v
That's an effect of
--dry-run
which specifically is used to display which tasks would be executed, so it is shown there.
s
And there is no option to not print these lines?
v
Why should they not get printed when you ask Gradle to print them?
What else do you want to achieve with
--dry-run
?
s
I would like to filter only for the warnings. When I
--dry-run
, I know that tasks will be skipped.
v
Use
tasks.configureEach { enabled = false }
instead of
--dry-run
Or
<http://tasks.help|tasks.help> { enabled = false }
as you only execute the
help
task anyway
s
Ok, but I would like to not modify the build in any way. The execution happens server side, and editing a source file will introduce configuration-cache misses, etc.
v
You could use an init script to do the same
s
I suppose I could build a custom toggle inside all the build scripts.
Ok
Thanks for these info
v
The init script to disable the help task or all tasks should be quite simple if you want to go that route. But either way, with an init script or with a toggle in the build scripts, configuration cache would not be reused either way anyway