-
Notifications
You must be signed in to change notification settings - Fork 18
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
chore: make cache keys cleaner #242
Conversation
✔️ Deploy Preview for api-clients-automation canceled. 🔨 Explore the source changes: 8ae1a2f 🔍 Inspect the deploy log: https://app.netlify.com/sites/api-clients-automation/deploys/6228a096e21a1500092f8b42 |
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.
This looks good to me.
key: | | ||
${{ env.CACHE_VERSION }}-${{ | ||
hashFiles( | ||
'clients/algoliasearch-client-java-2/client-predict/**', |
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.
didn't know java had the predict client already !
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.
ahaha yep that was a miss, it's fixed in #244
🧭 What and Why
🎟 JIRA Ticket: -
Changes included:
Because cache keys were unreadable and hard to iterate on when working on GitHub actions.
key
to only keep relevant datahashFiles
with multiple parametersIt is still pretty repetitive, but at least we can now read the file easier.
🧪 Test
CI :D