-
Notifications
You must be signed in to change notification settings - Fork 30
Experimental: use cargo-batch
to reduce CI build times
#244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
comments
It's either me dancing the https://github.com/playfulFence/esp-generate/actions/runs/18558236275 |
if ! command -v cargo-batch &> /dev/null; then | ||
cargo install --git https://github.com/embassy-rs/cargo-batch cargo --bin cargo-batch --locked --force | ||
fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shouldn't do this on the normal runners, the xtask should detect if cargo-batch is present and fall back to individual cargo commands otherwise, just like we do for esp-hal. forcing cargo-batch is not the best idea (what if you simply don't want it on your PC, or what if your antivirus decides to remove it suddenly?), we have the code to somewhat smartly generate the commands.
closes #242
We probably want to use
m1
runner for this to actually have any impact (?)