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
After successfully replacing rake with Build CLI Tool in Release workflow, it would great to replace rake in all other workflows as well, since the current implementation of the Build tool supports running in CI pipelines.
Another task would be having a way to have the job Swatinem/rust-cache@v2.7.3 to cache the Build of the CLI Tool to avoid compiling it on each run, similar to installing nj-cli and wasm-pack now.
The main difference is that those tools are registered on crates.io, whereas installing the CLI tool is always locally. We can try to change the build to run from Git URL and hope that will trigger the caching action. Otherwise, we may need to register the tool on crates.io if we want to save about 1.5 Minutes on each GitHub Action
Task:
Replace Rake in lint_master.yml
Replace Rake in pullrequest_check.yml
Remove build_cli_checks.yml
Cache CLI Tool binary to reduce building time.
The text was updated successfully, but these errors were encountered:
After successfully replacing rake with Build CLI Tool in Release workflow, it would great to replace rake in all other workflows as well, since the current implementation of the Build tool supports running in CI pipelines.
Another task would be having a way to have the job
Swatinem/rust-cache@v2.7.3
to cache the Build of the CLI Tool to avoid compiling it on each run, similar to installingnj-cli
andwasm-pack
now.The main difference is that those tools are registered on
crates.io
, whereas installing the CLI tool is always locally. We can try to change the build to run from Git URL and hope that will trigger the caching action. Otherwise, we may need to register the tool oncrates.io
if we want to save about 1.5 Minutes on each GitHub ActionTask:
lint_master.yml
pullrequest_check.yml
build_cli_checks.yml
The text was updated successfully, but these errors were encountered: