build: Speed up the infrastructure testing by removing compiling the CLI (which takes over 3 minutes)

[fundthmcalculus]

No description provided.

[janpieterz]

We should let people know, and can we confirm that this actually runs grpc 2 (feels weird to direct to a grpc-web samples directory) as well as let the team know? Everyone expects the CLI tests to run, so this is worth notifying in #engineering.

[fundthmcalculus]

Agreed. I wanted to run it by you before I post it to the broader channel. I should probably rename the folder, since it's really just NPM testing. I specifically went away from the CLI because of the amount of time it takes to run cargo build.

[tmarkovski]

I specifically went away from the CLI because of the amount of time it takes to run cargo build.

CLI can be installed using Homebrew. The service makes bottles for Linux x86 already, so it would just download and use it without compiling.

[fundthmcalculus]

I specifically went away from the CLI because of the amount of time it takes to run cargo build.

CLI can be installed using Homebrew. The service makes bottles for Linux x86 already, so it would just download and use it without compiling.

brew install actually installs via cargo, which doesn't fix the underlying problem of rust's painfully long compile times.

[tmarkovski]

brew install actually installs via cargo, which doesn't fix the underlying problem of rust's painfully long compile times.

Only if there's no bottles for the platform. Our CI creates bottles for Linux x86, so this shouldn't build the formula locally, just pull the binary.

[fundthmcalculus]

brew install actually installs via cargo, which doesn't fix the underlying problem of rust's painfully long compile times.

Only if there's no bottles for the platform. Our CI creates bottles for Linux x86, so this shouldn't build the formula locally, just pull the binary.

ZOOM. 13 seconds to set up homebrew AND the cli. 🚀