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

Pants

The caches have been baking all weekend, and we bump the cache keys frequently for other things

really? interesting... what other things?

Once third party jvm products stabilize it won't be necessary

lemme do a build and look at some analysis

Now I really want to know when and how rebasing is done in isolated

yes, building is the easiest way to get artifacts.

```fozzie:[~/src/foursquare.web][master]$ du -h -d 1 .pants.d/compile/jvm/zinc/
 45M	.pants.d/compile/jvm/zinc//isolated-analysis
 39M	.pants.d/compile/jvm/zinc//isolated-classes
  0B	.pants.d/compile/jvm/zinc//isolated-logs
 23M	.pants.d/compile/jvm/zinc//jars
108M	.pants.d/compile/jvm/zinc/```

Most of the size of the analysis appears to be the "internal apis"

but those would have been there before too

Building doesn't exactly give you artifacts, I thought we pre/post-process artifacts to and from the cache

What are we talking about exactly? these analyses look ok to me.

Interrupting a bit - does anyone object to a release tonight or tomorrow am - I'd preform it, go fetch has a bug that blocks using any remote artifact that uses relative imports

But there are serious perf regressions on fully cached builds

and we're sure this isn't the cache server?

I just did a fully-cached build of hfileserver and it was super fast.

55 seconds, 50 of which was fetching the 75 artifacts.