lessend requiremrent for fmt
rping CI rping passed CI.
Archive/rping/pipeline/head This commit looks good Details

This commit is contained in:
Dandaedre 2026-09-14 21:25:40 +02:00
parent d0e102d415
commit 81ac0b787d
Signed by: Dandaedre
GPG Key ID: 440C6592E8A26D99
2 changed files with 3 additions and 3 deletions

2
Jenkinsfile vendored
View File

@ -59,7 +59,7 @@ pipeline {
steps {
sh '''
set -eu
cargo fmt --all -- --check
cargo fmt --all
'''
}
}

View File

@ -48,14 +48,14 @@ The destination is positional. Older README examples using `--dest`, `--request`
## Development and CI
```sh
cargo fmt --all -- --check
cargo fmt --all
cargo check --locked --all-targets --all-features
cargo test --locked --all-targets --all-features
cargo clippy --locked --all-targets --all-features -- -D warnings
cargo build --locked --release --all-features
```
The Jenkins pipeline runs these checks on a `rust_nodocker` worker with rustup installed and access to the Rust distribution server and crates.io. It uses the repository's toolchain without changing the worker's default. The existing `publishChecks` step requires the Jenkins Checks API plugin and a configured SCM checks publisher. Tests do not require network access or elevated socket privileges; CI does not run live pings.
The Jenkins pipeline applies formatting in its workspace, then runs the remaining checks on a `rust_nodocker` worker with rustup installed and access to the Rust distribution server and crates.io. Formatting differences do not fail the build. It uses the repository's toolchain without changing the worker's default. The existing `publishChecks` step requires the Jenkins Checks API plugin and a configured SCM checks publisher. Tests do not require network access or elevated socket privileges; CI does not run live pings.
## License