acceptable-football-32760
03/01/2023, 9:17 AMpants package
caches the state of the environment to decide when to re-run. The following holds
./pants package <targetX> # proper building happens
./pants package <targetX> # no building happens
# close and open terminal, no code changes
./pants package <targetX> # again rebuilding
is that expected? I'm on 2.16.0dev7 and quite an old ./pants
launcher script (no scie-pants yet).
Thanks!happy-kitchen-89482
03/01/2023, 2:59 PMacceptable-football-32760
03/02/2023, 8:40 PMpex_binary
happy-kitchen-89482
03/02/2023, 8:43 PMhappy-kitchen-89482
03/02/2023, 8:43 PMacceptable-football-32760
03/02/2023, 9:36 PMfnm_multishells
in path change on every invocation (this is some artifact of the https://github.com/Schniz/fnm manager of node versions...)
Here are the logs: first build, second build (noop) and third build after reopening the terminal (I redacted some paths which are unimportant, sorry).
Can it be that the because of unrelated change in PATH
it gets re-run? In bazel
I believe the build --incompatible_strict_action_env=true
is responsible for being less sensitive to env changes...
Thanks!happy-kitchen-89482
03/02/2023, 10:04 PMacceptable-football-32760
03/03/2023, 7:08 AMincompatible_strict_action_env
in this Slack, I found -- guess what -- https://pantsbuild.slack.com/archives/C046T6T9U/p1647260136815439 😄 it's like I reteruned to the topic and completely forgot what I myself had on it 😄 Thanks once again!happy-kitchen-89482
03/03/2023, 3:33 PM