Assigned
Status Update
Comments
uc...@google.com <uc...@google.com>
je...@google.com <je...@google.com>
bi...@google.com <bi...@google.com>
bi...@google.com <bi...@google.com> #2
Hi Sergey, when adding integration test, I find ArgumentsGenerationTask is not cacheable(https://source.corp.google.com/aosp-androidx/navigation/navigation-safe-args-gradle-plugin/src/main/kotlin/androidx/navigation/safeargs/gradle/ArgumentsGenerationTask.kt;l=42;bpv=0;bpt=0 )
Could you make it cacheable?
Could you make it cacheable?
se...@google.com <se...@google.com> #4
Jeremy, will you be able to look at that?
hu...@google.com <hu...@google.com> #5
[Android Studio Build-and-Sync Fix-It Week] Moving to a more correct component for this bug.
jb...@google.com <jb...@google.com> #6
This was made cacheable in aosp/1726191.
Description
To test this, add a test for a project which uses the safe args plugin and ensure that the compile tasks, safe args plugin tasks, and other dependent resource tasks are relocated between builds.
More information:
We want to be sure that the Android Gradle Plugin has full coverage for cache relocatability going forward. We noticed there there were a few missing cases in test coverage for cache relocatability. It is important that tasks produce stable outputs that are relocatable between builds so that users can benefit from caching and remote caching.
Cache relocatability is explained here:
Here are some resources/examples to help write these tests:
This example test relocation using a real world project:
This example creates a configurable small sample project to test relocatability:
Here are the cache relocatability tests in the Android Gradle plugin: