cicd: Try using Next.js cache in CMS Docker build #62
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
felixmokross
force-pushed
the
improve-cms-docker-build
branch
from
adfe418 to
879e455
Compare
Owner
Author
|
Even though with the Depot builders via the Flyctl API I can't cache the build (Next.js cache, PNPM store), it is still faster than using Docker on GitHub Actions. Especially since extra steps are needed to make cache mounts cache across builds, the total runtime takes longer (up 60s extra overhead for extracting/saving the cache). Also layer caching seems to be slower than on Depot. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.