Hi!
I would like to make use of cargo-chief in the CI for unit tests stage, so I've prepared the docker image for the CI pipeline containing following two directives:
RUN cargo chef cook --clippy --all-targets --all-features --recipe-path recipe.json
RUN cargo chef cook --tests --benches --all-features --recipe-path recipe.json
In the pipeline I copy all the sources into the /app directory (where commands above took place) and run the CI commands. Clippy stage works like a charm - only my project is checked. When it comes to the unit test stage it runs the following command:
cargo nextest run --all-features --profile ci --config-file=.cargo/nextest.toml
But it does the compilation of all the dependencies. Only the downloading is skipped.
I wonder if I'm doing something wrong or nextest is incompatible with the cargo-chief?
Hi!
I would like to make use of cargo-chief in the CI for unit tests stage, so I've prepared the docker image for the CI pipeline containing following two directives:
In the pipeline I copy all the sources into the /app directory (where commands above took place) and run the CI commands. Clippy stage works like a charm - only my project is checked. When it comes to the unit test stage it runs the following command:
cargo nextest run --all-features --profile ci --config-file=.cargo/nextest.tomlBut it does the compilation of all the dependencies. Only the downloading is skipped.
I wonder if I'm doing something wrong or nextest is incompatible with the cargo-chief?