Hello folks,
I have a multi-module Gradle project with a decent number of files which I supposed potentially could have benefited from using the new --watch-fs feature. But, actual CI logs don’t show any usage of the FS retention on consecutive builds.
Starting a Gradle Daemon (subsequent builds will be faster)
Watching the file system is an incubating feature.
Spent 19 ms registering watches for file system events
Virtual file system retained information about 0 files, 0 directories and 0 missing files since last build
...
BUILD SUCCESSFUL in 1m 37s
4000 actionable tasks: 4000 from cache
Virtual file system retains information about 0 files, 0 directories and 0 missing files till next build
After reading the official documentation I concluded that feature is not applicable for CI systems as all FS changes are stored in the memory of the Gradle daemon process. Which according to my knowledge does not survive between CI system build runs.
To detect changes on the file-system, and to calculate what needs to be rebuilt, Gradle collects information about the file-system in-memory during every build (aka Virtual File-System ).
I’d appreciate it if somebody can confirm/deny the statement of the uselessness of using this option on CI systems. And if the VFS information gets persisted somewhere which place is it (I clean some of the .gradle/caches folders after each build)?
Thanks in advance!