@brettchabot Cache Gradle Managed Devices emulator snapshot. #2115
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It currently takes ~50 seconds on each CI run to boot the emulator
and save a snapshot.
This commit saves the snapshot to a github action cache, to save the
cost of booting on each run.
However, compressing and saving the snapshot to cache is also expensive (~30 seconds)
so we don't want to do this for every run. Ideally there would be a precise
mechanism for determining if the snapshot has changed. For now, just use a cache
key encorporating the date and the hash of the top level build.gradle file, so
the cache is generated every week.