#22946 Simplify Pants distributions for certain workflows (fat-pants) Issue created by sureshjoshi This has been discussed in the Slack, but I couldn't find an associated ticket. In short, I've proposed creating fat-pants releases, where we bundle the machinery to start Pants in a single-download. This does not include backends that download items at runtime - just the Jump/Python/Pants/etc to get going. See extra commentary about no-network workflows here: #22942 See dumb, old, public proof-of-concept here: https://github.com/sureshjoshi/assless-chaps In private repos, I have something like this I use currently - but it's only designed for exactly 1 person (me) and has zero backwards compat. In this workflow, instead of using the get-pants script, or downloading the scie-pants runner, to then kick off the rest of the workflow - you'd pull down the specific

pants-{version}-{arch}.scie

you want, and you'd be ready to go. pantsbuild/pants