CI: use cargo-chef for dependency build caching#97
Draft
Conversation
Due to an incorrectly changed caching behavior (inline without push) in the underlying docker-build composite action, the reusable-workflow using an older action is reverted to.
ezdac
force-pushed
the
ezdac/cargo-chef
branch
from
c2f3eb8 to
fda9e78
Compare
ezdac
force-pushed
the
ezdac/cargo-chef
branch
from
8db8b3a to
607f245
Compare
ezdac
force-pushed
the
ezdac/cargo-chef
branch
from
607f245 to
60bb792
Compare
Author
|
It seems that the |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Try out if cargo-chef can be used for two-stage rust builds in order to cache the first dependency-only build.
Currently we are doing this manually by copying individual folders and files in the docker-file.
This is coupled to the source-code, and will drift and potentially break when file-changes in source are not reflected in the
docker file and thus it's layer caches.
cargo-chef promises to automate this process by constructing a build-recipe and later consuming it in a dependency-only build step that can be individually layer-cached.
This PR tries out wether that will work with our codebase.