Hi, I am trying out the SCIE pants and specify pan...
# general
b
Hi, I am trying out the SCIE pants and specify pants 2.16.0rc0 in pants.toml. This file is put under a subdirectory of my repo so before I have an env var PANTS_TOML to indicate that. however I found this is not going to work. If I move pants.toml to the top level it would work.
The problem I am seeing is
Copy code
The `pants.toml` at /Users/xxxx/xxxx/xxxxx/pants.toml has no `pants_version` configured in the `GLOBAL` section.
Would you like set `pants_version` to the latest stable release? (Y/n):
and if I select no, it would crash with
Copy code
ERROR: Failed to establish atomic directory /Users/xxxx/Library/Caches/nce/142382d6e3ac0960e7d4f81b9df9de9559b7ac698db13d20cbd0e4aa57f68c1d/locks/configure-a04b16475909adc53343e9b2a72885b57d783b5743b4fbcdad57d8d31e81ace7. Population of work directory failed: Boot binding command failed: exit status: 1
e
The scie pants binary does in fact require
pants.toml
to be at the root of the repo as things stand. It is true the scie pants binary should be fully backwards compatible with the
./pants
script and so this is a bug, but I think it's also true that we've never encountered someone not placing
pants.toml
at the root of the repo. So, I'd file an issue in the pantsbuild/scie-pants repo, but you should also strongly reconsider setting up your repo this way. What is the motivation?
b
we are trying to share the building tool among different repositories so would like to keep them using the same one instead of each using its own pants setup
e
Ok, that is definitely not expected or encouraged.
If the
pants_version
is the same, the tool is shared.
As far as wanting to shared the rest of the config ... Definitely a new one. 1st in 13 years.
At any rate, as I said this is a bug; so please file an issue so it's tracked.
b
sure. will do
e
You probably want to mention this fact about your repos if you need to report other issues since it is so non standard.