# general
https://www.pantsbuild.org/v2.15/docs/using-pants-in-ci this works fine on desktop/local dev, not sure what to do about CI, specifically, how to make this work in CI. Specifically, caching the pants script and a particular version of pants. https://www.pantsbuild.org/v2.15/docs/using-pants-in-ci Based on my testing, when using the launcher, pants is no longer cached under
The pants version is set the same way as always via pants.toml
. The cache is at ~/.cache/nce on Linux. See: https://github.com/pantsbuild/scie-pants/issues/31 for the issue tracking integration work with the GH action Pants provides.
👍 1
is non obvious for people who look under the
folder ( I do... I know I am weird this way). I would suggest that this will move under
or even
this way, the existing guidance and usage patterns for caching pants version is CI holds and doesn't need to change.
lmk if u want me to open a ticket for this, happy to do so (not sure which repo...)
Well, the existing https://github.com/pantsbuild/scie-pants/issues/31 covers part of this for folks who use the action supplied by Pants. If you don't want to use that action, then yeah, it needs to be documented at the very least or maybe moved. You can file a new issue in scie-pants. If the answer ends up being documentation (~/.cache/pants/setup isn't necessarily obvious either, though clearly more obvious), then I can transfer to Pants, but the answer may also be moving the default which would be a scie-pants change. FWIW you can use
today if you want.