New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gradle task processGoogleServices is never cached #58
Comments
@davidvavra |
These tasks are run everytime (never UP-TO-DATE):
So it's not possible to check if json hasn't changed and if not, don't generate XML again? |
Seems like this is fixed in 4.3.0? After upgrading, I see that those tasks are finally marked as UP-TO-DATE by Gradle in a no-change build. |
Seems to be fixed with 4.3.0 for I've created a dedicated issue here: #68 |
I confirm that 4.3.0 fixed it. Right now the problem is with |
I tried to inspect my gradle build based on a tip from I/O talk: Run gradle build two times and see which tasks are not UP-TO-DATE. And I found the culprit: google-services-plugin.
I run
./gradlew assembleProdDebug
two times without any changes and task:app:processProdDebugGoogleServices
is not UP-TO-DATE. It causes other tasks down the road to execute again and it's slowing down every build.Can google-services-plugin be made cacheable?
The text was updated successfully, but these errors were encountered: