So far I'm using the Rust Docker image for Debian Buster and running the following steps:
rustfmt
clippy
cargo check
cargo test
cargo build
The clippy step is run with the -D flag which means the run will fail if a clippy warning is encountered.
The steps are run for amd64 and arm64 architectures. The cargo check is currently failing due to a lint warning in peach-lib (I'll fix that once this PR is merged and then fine-tune the CI config if necessary).
Once thing I noticed after adding the arm64 part to the config is that the amd64 pipeline keeps running after it fails the cargo check step; it doesn't move onto the next steps but it doesn't stop either...it keeps ticking along and needs to be manually cancelled. I'd like to figure out how to prevent that happening.
Here's a PR to address [issue #98](https://git.coopcloud.tech/PeachCloud/peach-workspace/issues/98).
Drone has been quite easy to setup and navigate (https://build.coopcloud.tech/).
So far I'm using the Rust Docker image for Debian Buster and running the following steps:
- `rustfmt`
- `clippy`
- `cargo check`
- `cargo test`
- `cargo build`
The `clippy` step is run with the `-D` flag which means the run will fail if a `clippy` warning is encountered.
The steps are run for `amd64` and `arm64` architectures. The `cargo check` is currently failing due to a lint warning in `peach-lib` (I'll fix that once this PR is merged and then fine-tune the CI config if necessary).
Once thing I noticed after adding the `arm64` part to the config is that the `amd64` pipeline keeps running after it fails the `cargo check` step; it doesn't move onto the next steps but it doesn't stop either...it keeps ticking along and needs to be manually cancelled. I'd like to figure out how to prevent that happening.
Yeah it's pretty powerful! Maybe tomorrow I'll spend some time trying to understand why it hangs after the amd64 run (without moving onto the arm64 section).
Yeah it's pretty powerful! Maybe tomorrow I'll spend some time trying to understand why it hangs after the amd64 run (without moving onto the arm64 section).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
notplants
Here's a PR to address issue #98.
Drone has been quite easy to setup and navigate (https://build.coopcloud.tech/).
So far I'm using the Rust Docker image for Debian Buster and running the following steps:
rustfmtclippycargo checkcargo testcargo buildThe
clippystep is run with the-Dflag which means the run will fail if aclippywarning is encountered.The steps are run for
amd64andarm64architectures. Thecargo checkis currently failing due to a lint warning inpeach-lib(I'll fix that once this PR is merged and then fine-tune the CI config if necessary).Once thing I noticed after adding the
arm64part to the config is that theamd64pipeline keeps running after it fails thecargo checkstep; it doesn't move onto the next steps but it doesn't stop either...it keeps ticking along and needs to be manually cancelled. I'd like to figure out how to prevent that happening.wow so cool that a 77 line yml file can do all that
Yeah it's pretty powerful! Maybe tomorrow I'll spend some time trying to understand why it hangs after the amd64 run (without moving onto the arm64 section).