Sorry if this is answered on the docs, I wasn't ab...
# general
a
Sorry if this is answered on the docs, I wasn't able to find an answer there. Is there a way to attach build metadata that gets shared with remote caching providers? I'm looking to differentiate Pants cache usage across multiple repos. And I'd like to do something like Bazel's
--build_metadata=REPO=<name>
(e.g. BuildBuddy docs).
And if the answer is no, but a "good first issue" kind "no," I could try to take a whack at it 😄
Loooooking at Bazel code this looks like a totally different protocol than the normal RBE / remote caching stuff. AKA: an entirely different
build_event_stream.proto
file that Pants doesn't look at right now. I have a cheeky feeling this isn't a "good first issue" kind of no
h
If it's not in the standard REAPI, then Pants likely doesn't support it, but I'll let people who know more than I do about it have the final word
👍 1
b
https://www.pantsbuild.org/2.19/reference/global-options#remote_instance_name might work for what you want, depending on the server? Maybe not so much metadata for analytics though
a
I can experiment with that. We're using BuildBuddy and have just made separate orgs for now to split out reporting by department. I'll keep on digging in! Thanks as per usual for being so responsive here 🙏