Is there an easy way to make a `pants` release for...
# development
c
Is there an easy way to make a
pants
release for testing locally, so I might avoid a mistake like https://github.com/pantsbuild/pants/pull/18342 in the future?
e
The easiest way is probably running
./build-support/bin/release.sh build-local-pex
That will net you a Pants PEX under
dist/
that you can run in place of either the
./pants
script or the scie-pants binary in order to perform the test.
c
That sounds like exactly what I need, thanks!
b
Honestly the pants repo should lint/test this pitfall.
c
There's actually another pitfall in this PR. It's missing a BUILD file in
python/pants/backend/experimental/tools/yamllint
, but the CI doesn't seem to care. I only noticed when trying to build this local release.
b
tailor --check
should catch that
c
Maybe we should run that in CI?
b
AFAIK We do 😳
c
But the CI was green before I added the BUILD file 😕
b
Hence the 😳
c
Or maybe the CI wasn't green and I just didn't scroll down enough? I'm just generally confused, I think 😄
b
I've seen GitHub report green on a commit but red on a PR