-
Notifications
You must be signed in to change notification settings - Fork 110
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
GitHub: use maintained version of docker layer cache action #471
Conversation
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.
FWIW, jpribyl/action-docker-layer-caching
has some sort of CI failure itself. Might be inconsequential: https://github.com/jpribyl/action-docker-layer-caching/actions?query=workflow%3A%22Readme+Test%22
@@ -42,7 +42,8 @@ jobs: | |||
uses: actions/checkout@v3 | |||
|
|||
- name: docker image cache | |||
uses: satackey/action-docker-layer-caching@v0.0.11 | |||
uses: jpribyl/action-docker-layer-caching@v0.1.1 | |||
continue-on-error: true |
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.
After some reading about this workflow, I saw this comment. Adding a link in case it's relevant for reviewer to assess soundness
We just use this caching step to make sure we don't hit the Docker Hub pull limit. We don't actually care that much if it fails from time to time, as long as it does its job most of the time. |
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.
👍🏽
Looks like the old
satackey/action-docker-layer-caching
action has finally stopped working: https://github.com/lightninglabs/taproot-assets/actions/runs/5999726192/job/16270427354We update to a forked version that is maintained and also allow the test to continue if the caching fails.