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

Pants

Hi all! I wanted to understand how caching and dependencies work, for example when running in a CI. I find myself a lot of times modifying a config file in the repo (declared as a `resources`) and I’d like to avoid rerunning unnecessary tests when this happens (but also I want to run a few relevant ones). I was thinking of setting up a special set of “config tests” but I am not sure what happens if the only changed files are for example yaml included in resources. Can somebody shed light on this?

The right thing should happen. The sources in a `resources` target participate in fingerprinting just like any other sources.

So as long as your test depends on the `resources` target (presumably via explicit dep, since we don't infer deps on resource files) then invalidating the resource should invalidate the tests that depend on it, and only those tests.