https://pantsbuild.org/ logo
#development
Title
# development
c

clever-toothbrush-13797

02/23/2023, 1:20 PM
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

enough-analyst-54434

02/23/2023, 1:29 PM
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

clever-toothbrush-13797

02/23/2023, 1:31 PM
That sounds like exactly what I need, thanks!
b

bitter-ability-32190

02/23/2023, 2:11 PM
Honestly the pants repo should lint/test this pitfall.
c

clever-toothbrush-13797

02/23/2023, 2:12 PM
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

bitter-ability-32190

02/23/2023, 2:13 PM
tailor --check
should catch that
c

clever-toothbrush-13797

02/23/2023, 2:15 PM
Maybe we should run that in CI?
b

bitter-ability-32190

02/23/2023, 2:15 PM
AFAIK We do 😳
c

clever-toothbrush-13797

02/23/2023, 2:15 PM
But the CI was green before I added the BUILD file 😕
b

bitter-ability-32190

02/23/2023, 2:16 PM
Hence the 😳
c

clever-toothbrush-13797

02/23/2023, 2:24 PM
Or maybe the CI wasn't green and I just didn't scroll down enough? I'm just generally confused, I think 😄
b

bitter-ability-32190

02/23/2023, 2:42 PM
I've seen GitHub report green on a commit but red on a PR
5 Views