Add CI #10

New issue

Open

opened 2025-10-08 20:32:26 +02:00 by federico · 1 comment

federico commented

2025-10-08 20:32:26 +02:00

Collaborator

For the starting point of a continuous integration pipeline, I'd like to have jobs that do this:

cargo build or cargo check; the project is small enough that we can build every time.
cargo test
cargo fmt -- --check not to reformat, but to check that one doesn't commit inconsistently-formatted code
cargo clippy

Later:

Any integration tests that happen outside of cargo test
cargo-deny - Checks that there are no dependencies with published vulnerabilities, and can do checks for license compatibility.
cargo doc to have documentation on the internals. This is nice for newcomers to browse.
Render and publish the installation docs when they are written? Make that site a self-hosted fipamo site?
Builds for the various configurations that you want to support: alpine/musl, glibc, etc.

For the starting point of a continuous integration pipeline, I'd like to have jobs that do this: * `cargo build` or `cargo check`; the project is small enough that we can `build` every time. * `cargo test` * `cargo fmt -- --check` not to reformat, but to check that one doesn't commit inconsistently-formatted code * `cargo clippy` Later: * Any integration tests that happen outside of `cargo test` * [`cargo-deny`](https://github.com/EmbarkStudios/cargo-deny) - Checks that there are no dependencies with published vulnerabilities, and can do checks for license compatibility. * `cargo doc` to have documentation on the internals. This is nice for newcomers to browse. * Render and publish the installation docs when they are written? Make that site a self-hosted fipamo site? * Builds for the various configurations that you want to support: alpine/musl, glibc, etc.

ro commented

2025-10-09 17:39:40 +02:00

Collaborator

I'm open to all this, but as I'm still pretty new to Rust, I'll need some guidance on how to get these processes set up.

I'm doing deploys manually right now, so I definitely want to learn how to automate that flow.

I'm open to all this, but as I'm still pretty new to Rust, I'll need some guidance on how to get these processes set up. I'm doing deploys manually right now, so I definitely want to learn how to automate that flow.

No labels

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: projects/love_fipamo#10

No description provided.

Rows
Columns