Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Design mechanism to keep `pants.pex` up-to-date #8209
We must now depend on
How will this work in CI?
Problem: the test shards won't have a cache with all the generated pants.pex fingerprints, and we don't want them to ever bootstrap. They should use whatever is uploaded.
Possible solution: check for the env var
I'm implemented parts 1 and 2 through #8183, i.e. the script to generate and cache
Now, we have to figure out step 3: when to actually trigger
There appear to be two approaches:
We could technically do a 3rd approach of modifying
Is there a reason we can't do this in
It seems like it's perhaps possible to run the pex bootstrap script where we obtain the path to
That code will already be running inside the remoting sandbox, because it's part of what PyTest itself is running.
@Eric-Arellano : Re:
It's also more likely that doing it in this location could evolve into a more native "pants startup hooks" facility (although it's not clear how end users would use it...).