Description
As discussed in #114 (comment), we are currently using devcontainers/ci which ensures maximum environment consistency but lacks Cargo dependency caching. This leads to rebuilding all crates from scratch on every run.
While Option A (current fad97eb) is fine for now, we should consider migrating to Option B if CI times significantly increase.
Proposed Changes (Option B)
- Switch the
Build and Test job from devcontainers/ci to a standard container: runner using our GHCR image.
- Integrate
Swatinem/rust-cache@v2 to cache the target/ directory and Cargo registry.
Pros
- Reduction in CI runtime.
- Faster feedback loop for Pull Requests.
Cons
- Requires the Dev Container image to be pre-published in GHCR to work.
- Slight risk of environment drift if the Dockerfile is changed without updating the image.
Note: This is a "Note Bene" issue to be implemented when build times exceed a reasonable threshold.
Description
As discussed in #114 (comment), we are currently using
devcontainers/ciwhich ensures maximum environment consistency but lacks Cargo dependency caching. This leads to rebuilding all crates from scratch on every run.While Option A (current fad97eb) is fine for now, we should consider migrating to Option B if CI times significantly increase.
Proposed Changes (Option B)
Build and Testjob fromdevcontainers/cito a standardcontainer:runner using our GHCR image.Swatinem/rust-cache@v2to cache thetarget/directory and Cargo registry.Pros
Cons
Note: This is a "Note Bene" issue to be implemented when build times exceed a reasonable threshold.