Kind of wanted to do it, but clippy needs all sorts of dependencies at the moment so building a container for it is going to take some space. You also need to do nightly because it's nightly only. Can't use muslrust because clippy doesn't support static linkage, and that probably makes sense. It's doing some fancy stuff with the compiler at runtime anyway.
That means that CI will have to use something naive like:
FROM rustlang/rust:nightly
RUN cargo install clippy
CMD cargo-clippy
That image is 1.5GB alone, but it does work:
docker build . -t clux/clippy
cd somesrcdir
docker run -v $PWD:/volume -w /volume -it clux/clippy cargo clippy
Theoretically, we could push that image as nightly cron job on travis, have circleci pull in both muslrust and that image, but it feels so inefficient that I'll just leave this here for a future think about.
Essentially, not sure if clippy is better suited as an editor tool to occasionally look at, than spending all these resources to get mostly annoyed by it in a slow feedback loop CI.
Kind of wanted to do it, but clippy needs all sorts of dependencies at the moment so building a container for it is going to take some space. You also need to do nightly because it's nightly only. Can't use muslrust because clippy doesn't support static linkage, and that probably makes sense. It's doing some fancy stuff with the compiler at runtime anyway.
That means that CI will have to use something naive like:
That image is 1.5GB alone, but it does work:
Theoretically, we could push that image as nightly cron job on travis, have circleci pull in both muslrust and that image, but it feels so inefficient that I'll just leave this here for a future think about.
Essentially, not sure if
clippyis better suited as an editor tool to occasionally look at, than spending all these resources to get mostly annoyed by it in a slow feedback loop CI.