azure-pipelines
azure-pipelines copied to clipboard
crate-ci
Easy continuous integration for Rust projects with Azure Pipelines
Could you tag the current HEAD of master as "v0.5", or create a branch similar to v0.4? It makes it safer to depend on the repo.
spontoreau's Task might be a good basis for us. See discussion below # Original Including - Repo name(s) - One or more repos - One or more branches - Folder...
Adds a parameter 'test_args_raw' that allows users to pass raw args/options to cargo/libtest. It also refactors how conditional checks are handled: rather than checking all combinations of bools for each...
This PR does two things. First, it adds a new smoke test to the mix: `cargo check -- -D warnings`, which will error on _any_ warning from `rustc`. Second, it...
Cargo check -h shows that the --all flag has been depreacated and replaced with the --workspace flag. Also https://github.com/rust-lang/cargo/issues/5015 shows hat the --no-default-features is currently broken so we thought that...
We recently made the decision to have this repository provide building blocks for CI (and a single, "80%" default template), since we found it too difficult to expose all the...
Considerations - Emitting JUnit reports - Emitting coverage (gathered in which way?) - Maintaining support for `cargo test`'s features that are relevant for CIs Possibilities - Contribute JUnit support to...
Inputs - Allow evolution - Don't break CIs - Simple, naiive case should not lead user to unstable resources - If using branches for different versions, someone might naiively grab...
Would be great to turn CI red on vulnerable dependencies.
