-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add inputs.cache-save-always
#34
Commits on Jan 18, 2024
-
Adds an input that borrows the `save-always` input from [v4 of `actions/cache`][0], which will run the post step to save the cache even if a failure occurs. Using the added `cache-save-always` input saves the cache when a build fails, which will speed up subsequent runs which restore the partial build. This comes at the cost of requiring a build when there is an exact `key` match, since the cache from a failed build will have the same `key` as a completed build. [0]: https://github.com/actions/cache/tree/main#v4
Configuration menu - View commit details
-
Copy full SHA for 60924a3 - Browse repository at this point
Copy the full SHA 60924a3View commit details -
Configuration menu - View commit details
-
Copy full SHA for 896bf2a - Browse repository at this point
Copy the full SHA 896bf2aView commit details
Commits on Jan 22, 2024
-
Configuration menu - View commit details
-
Copy full SHA for ffa7c66 - Browse repository at this point
Copy the full SHA ffa7c66View commit details -
Use
-partial
key to no-op after full cache-hitSaves the set of build artifacts after a build failure with a `-partial` suffix on the cache key. A full cache-hit will therefore only occur when restoring the cache saved after a successful build, allowing for the subsequent `stack build` and cache-save steps to be skipped.
Configuration menu - View commit details
-
Copy full SHA for 629a6a9 - Browse repository at this point
Copy the full SHA 629a6a9View commit details -
Set suffix using conditionally run step
Status check functions can only be used in `if` conditionals, so the use of a cache key suffix needs to be determined in a conditionally-run step.
Configuration menu - View commit details
-
Copy full SHA for dd40c85 - Browse repository at this point
Copy the full SHA dd40c85View commit details -
Revert "Set suffix using conditionally run step"
This reverts commit dd40c85.
Configuration menu - View commit details
-
Copy full SHA for c6b9b20 - Browse repository at this point
Copy the full SHA c6b9b20View commit details -
Revert "Use
-partial
key to no-op after full cache-hit"This reverts commit 629a6a9.
Configuration menu - View commit details
-
Copy full SHA for 58fa478 - Browse repository at this point
Copy the full SHA 58fa478View commit details -
Extend conditional in build/save-cache steps
Checks that the workflow has not been cancelled (i.e., is succeeding or failed) and that `cache-save-always: true` when building and saving the cache. This extends the existing conditional on the `cache-hit` outputs, making the previously-implied `success()` check explicit. When `cache-save-always: false`, the default behavior is unchanged for the action: steps either no-op if a cache-hit occurred, or build and save otherwise. When `cache-save-always: true`, a building and saving the cache occurs on success or failure.
Configuration menu - View commit details
-
Copy full SHA for 59b90b6 - Browse repository at this point
Copy the full SHA 59b90b6View commit details
Commits on Jan 23, 2024
-
Configuration menu - View commit details
-
Copy full SHA for d36a2d5 - Browse repository at this point
Copy the full SHA d36a2d5View commit details