Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

Hello, I have a question regarding the `clean-all` goal.
It seems that if I compile some target, then clean-all and then compile again the artifacts are still taken from the .cache folder.
If I `rm -rf .cache` that a recompile really happens.
So what’s the purpose of clean-all (other than closing open `nailgun` processes) and what’s the way to force recompile?

`./pants clean-all` wipes out `.pants.d`, which is where zinc incremental compile state and other non-cacheable things are

the content of `.pants.d` is much more likely to have "issues" than the cache, as the cache is immutable

if you want to skip using the cache, you can use `--cache-ignore`

(and pass it for specific tests if need be)