With the introduction of GH Actions in #350, we still have some performance that could be gained when building the Release.
Since the jobs don't share the files nor the tools we currently checkout the code a second time and when cargo build is invoked the cargo updates the registry.
This potentially could be improved by sharing artefacts or using a cargo caching action.
Resources:
With the introduction of GH Actions in #350, we still have some performance that could be gained when building the Release.
Since the jobs don't share the files nor the tools we currently checkout the code a second time and when
cargo buildis invoked the cargo updates the registry.This potentially could be improved by sharing artefacts or using a cargo caching action.
Resources:
jobin the cache key, but do check out Do not appendprocess.env.GITHUB_JOBto the cache key ifkeyis set Swatinem/rust-cache#6 )