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

Pants

`webpack` must be a task you guys implemented?

But even just `./pants resolve ::`, I'm not seeing a nice no-op, it does stuff. I've got a fresh AMI ready, is there anything you recommend I try?

At a high level tho, was just wondering if there is any "machine identifier" hash or anything anywhere, that would make my scenario not possible.

again, which things miss cache is the relevant bit

there is not... but some things are just not cached

i don't know if managed dependencies has good support for caching

Ok, i can start with the ivy resolve and narrow down exactly why its not no-oping. Also I guess there is a difference between "no-op" and "it did stuff, but didnt redownload deps". Ideally I want it to no-op.

but in general, the ivy cache key is dependent on the entire context: so if you run `./pants resolve blah::` and then `./pants resolve ::`, those are probably different keys.

Yeah our command lines are always the same between runs

<@U06A03HV1> I think what we’re talking about *should* be cached, b/c after running twice the second time is a noop, there’s def sth different b/w snap AMI, restore, run vs. run twice on same box

right but then the third run would also be slow? or at least not no-op

Right, the 3rd run (2nd on that box) is super fast

yes, which has nothing to do with the cache, and everything to do with whether pants knows the target has already been built in the workspace

3rd run, very pretty: <https://gist.github.com/MasterDDT/51baad36ad65603c5af023a1905eca97>

which is what is referred to as "invalidation"

invalidation occurs entirely within `.pants.d`.

The entire `.pants.d` dir should be preserved between runs

The only thing that changes is that the entire `/` happens to be on a different box

the contents of `.pants.d` isn't really portable.

So i poked around ivy and see things like this in ```&lt;ivy-report version="1.0"&gt;
        &lt;info
                organisation="internal"
                module="f7f5752499af315ad05b6e146c08f74072799996-resolve"
                revision="working@ip-10-0-4-245"
                conf="default"
                confs="default"
                date="20170302212331"/&gt;``` in `.pants.d/ivy/f7f5752499af315ad05b6e146c08f74072799996 &gt; less resolve-report-default.xml`

i'm actually surprised it works at all if you move that.

I see, its not portable because of hashes on machine, like ^?

that hash might be identical across machines, but it refers to something sitting in your ivy cache

if the entry in the ivy cache doesn't exist on the machine, you'll have to rerun it