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
Is your feature request related to a problem? Please describe.
In our CI/CD pipeline, every time we run moon ci, MoonRepo re-installs all configured binaries. In the case of trusted-signing-cli, this results in Cargo throwing an error because the binary already exists:
▪▪▪▪ cargo binstall
INFO resolve: Resolving package: 'trusted-signing-cli'
WARN The package trusted-signing-cli v0.5.0 will be installed from source (with cargo)
Updating crates.io index
error: binary `trusted-signing-cli` already exists in destination
Add --force to overwrite
ERROR Cargo errored! ExitStatus(unix_wait_status(25856))
Describe the solution you'd like
It would be great if MoonRepo could either:
Automatically detect that the binary already exists and either skip the installation step, or
Provide an option to automatically pass the --force flag for certain binaries in the configuration (for example, via an additional property for each bin).
Ideally, this behavior should be configurable per binary, allowing users to decide whether to force reinstall or simply skip if the binary is already present.
So it looks like binstall doesn't error if the package already exists:
~/Projects/moon fixes-0303 ± cargo binstall cargo-nextest
INFO resolve: Resolving package: 'cargo-nextest'
INFO resolve: cargo-nextest v0.9.92 is already installed, use --force to override
INFO Done in 841.440792ms
~/Projects/moon fixes-0303 ± cargo binstall cargo-nextest
INFO resolve: Resolving package: 'cargo-nextest'
INFO resolve: cargo-nextest v0.9.92 is already installed, use --force to override
INFO Done in 509.549625ms
I guess this error is because trusted-signing-cli already exists and wasn't installed through binstall.
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
In our CI/CD pipeline, every time we run moon ci, MoonRepo re-installs all configured binaries. In the case of trusted-signing-cli, this results in Cargo throwing an error because the binary already exists:
Describe the solution you'd like
It would be great if MoonRepo could either:
Ideally, this behavior should be configurable per binary, allowing users to decide whether to force reinstall or simply skip if the binary is already present.
Describe alternatives you've considered
Additional context
.toolchain.yml:
The text was updated successfully, but these errors were encountered: