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

Pants

(I can just read the md though, it's fine)

OK, I think I have more understanding with which to read more documentation

Our documentation still has a lot to be desired, but we make up for it in friendliness!

Wow, github has been hard down for a while

<@U0JSN507N>: I plan to make some major improvements to the Pants documentation. I’d be really interested in learning from your experience with them about what’s good and (more importantly) what’s missing or poorly done.

<@U054MQUPL>: Any plans to fix this in the near future? <https://github.com/pantsbuild/pants/issues/2659>

It's been a major hassle for us, and if it's not on your roadmap I'm going to fix it

<@U053HNE90>: i'm working on <https://github.com/pantsbuild/pants/issues/1640> ... but as a sidenote: how would you feel about globally enabling a local cache by default. would address <https://github.com/pantsbuild/pants/issues/2683>, and others

for reference: we have it disabled for a few of our internal tasks, but everything other than ivy in core pants is now cache safe

Yeah I think everything should be cached by default and we should just fix any straggler tasks that don't yet do so correctly

<@U051221NF>: I started a 'cookbook' style document, but haven't made too much headway  <https://docs.google.com/document/d/1x4N1NFALYFwq6O1oTTa8KRRDYBQNqsCjR0yCg4GTEtg/edit>

ThePantsCookbook.txt

Also I think Ivy could be made globally cache safe with some relatively simple XML parsing + path rebasing

Though it might not be worth it to do so if we're just going to be rewriting it anyway

and putting all of the artifacts in the resolve.

putting all of the fetched artifacts in the cache