-
Notifications
You must be signed in to change notification settings - Fork 625
dataconnect: github actions cache key fix #6829
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
Conversation
…s to verify that they run correctly.
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
Size Report 1Affected ProductsNo changes between base commit (3d41253) and merge commit (4718073).Test Logs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes a warning in the GitHub Actions workflow related to missing keys during nightly runs by replacing references to skipped step outputs with hard-coded cache key prefixes suffixed by the unique run ID.
- Updated the Gradle cache key to use a fixed prefix concatenated with the GitHub run ID.
- Updated the AVD cache key to include the Android emulator API level and the GitHub run ID.
Comments suppressed due to low confidence (1)
.github/workflows/dataconnect.yml:166
- [nitpick] Consider adding a hyphen after 'api' (e.g., 'api-${{ env.FDC_ANDROID_EMULATOR_API_LEVEL }}') to improve readability and consistency in the cache key format.
key: avd-cache-zhdsn586je-api${{ env.FDC_ANDROID_EMULATOR_API_LEVEL }}-${{ github.run_id }}
…D" step by using `cache-matched-key` instead of `cache-hit` See https://github.com/actions/cache/tree/main/restore
Coverage Report 1Affected Products
Test Logs |
This fixes the "Warning: Key is not specified" warning in the scheduled nightly runs in the "Save Gradle cache" and "Save AVD cache" steps of the dataconnect github actions workflow. The problem was that it was defining the key as
${{ steps.restore-gradle-cache.outputs.cache-primary-key }}
and${{ steps.restore-avd-cache.outputs.cache-primary-key }}
, respectively, but since those dependent steps were explicitly skipped in nightly runs their outputs were not defined.