Cache rock build results for register-typed rocks#899
Conversation
|
Can we add an option to skip the cache and rebuild the rock regardless? since some rocks don't have everything pinned and the output can change from one build to the next even if the content has not changed. |
In that case you can go to cache setting page and delete the cache which will force it to rebuild the rock. https://github.com/canonical/wordpress-k8s-operator/actions/caches |
# Conflicts: # dist/build/index.js # dist/build/index.js.map # docs/changelog.md
Test results for commit 504507aTest coverage for 504507a Static code analysis report |
Test results for commit 504507aTest coverage for 504507a Static code analysis report |
Test results for commit 504507aTest coverage for 504507a Static code analysis report |
Test results for commit 504507aTest coverage for 504507a Static code analysis report |
Test results for commit 504507aTest coverage for 504507a Static code analysis report |
Test results for commit 504507aTest coverage for 504507a Static code analysis report |
Applicable spec:
Overview
Caching rock build results to speed up the CI pipeline.
The rocks are cached if they:
The cache is invalidated and the rocks are rebuilt when:
Rationale
Workflow Changes
Checklist
urgent,trivial,complex)