You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #429 we started saving the Docker build cache during the build workflow. We discussed that the size of the Docker cache may end up causing issues and it has. Because it's ~9GB, the docker cache will often cause all other caches to be purged and, at least once, has failed to save seemingly due to its size. In addition, it takes about 9.75 mins to save the cache to GH caches. We should go ahead and implement the Runs-On S3 fast cache action to get around these issues.
DOD
The build workflow authenticates with AWS and writes caches to S3
The S3 bucket is configured to delete objects a day after their creation
We could instead use the AWS authentication to delete the caches during the build itself, but that requires more permissions on S3 and is less straight-forward to implement
Test Strategy/Script
View the latest build and verify the cache actions are from the runs-on/cache action
Confirm the caches saved to AWS are < 1 day old
The text was updated successfully, but these errors were encountered:
Also sets our docker container builder to use the fully-qualified name
for the moby/build-kit image to workaround the Docker authentication
issue noted in #331.
Future improvements:
- Update our GH ARC runner set to automatically auth with S3 instead of
using access keys that have to be rotated manually
Description
In #429 we started saving the Docker build cache during the build workflow. We discussed that the size of the Docker cache may end up causing issues and it has. Because it's ~9GB, the docker cache will often cause all other caches to be purged and, at least once, has failed to save seemingly due to its size. In addition, it takes about 9.75 mins to save the cache to GH caches. We should go ahead and implement the Runs-On S3 fast cache action to get around these issues.
DOD
Test Strategy/Script
runs-on/cache
actionThe text was updated successfully, but these errors were encountered: