As I reported in #101 we have issues when using gradle remote build cache: Sometimes (not always) we get cache misses due to fingerprint differences for options.compilerArgumentProviders.errorprone$0 and options.compilerArgumentProviders.errorprone$0.errorproneOptions.
I was not very successful with debugging the issue (it is non-trivial). Using the changes in this PR, I am no longer seeing these fingerprint differences between CI and developer machines. It has been consistently working for us for the last 100+ builds.
Feel free to deny this PR or request more changes if you don't feel confident about it @tbroyer
As I reported in #101 we have issues when using gradle remote build cache: Sometimes (not always) we get cache misses due to fingerprint differences for
options.compilerArgumentProviders.errorprone$0andoptions.compilerArgumentProviders.errorprone$0.errorproneOptions.I was not very successful with debugging the issue (it is non-trivial). Using the changes in this PR, I am no longer seeing these fingerprint differences between CI and developer machines. It has been consistently working for us for the last 100+ builds.
Feel free to deny this PR or request more changes if you don't feel confident about it @tbroyer