Drone CI build pipeline #101
No reviewers
Labels
No Label
bug
documentation
duplicate
enhancement
help wanted
invalid
maintenance
peach-lib
peach-network
peach-oled
peach-stats
peach-web
question
refactor
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: PeachCloud/peach-workspace#101
Loading…
Reference in New Issue
No description provided.
Delete Branch "drone_ci_test"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
rustfmt
clippy
cargo check
cargo test
cargo build
The
clippy
step is run with the-D
flag which means the run will fail if aclippy
warning is encountered.The steps are run for
amd64
andarm64
architectures. Thecargo check
is 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
arm64
part to the config is that theamd64
pipeline keeps running after it fails thecargo 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.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).