Set BUILDBUDDY_RUN_ID env var

[tylerwilliams]

I think this should be set in the env so that non-bazel tools can pick it up and send it back via PARENT_RUN_ID metadata to show up as linked workflow child invocations. LMK if there's a better way / something I'm missing here?

[bduffany]

I think you're looking for BUILDBUDDY_INVOCATION_ID which should already be set to the parent invocation ID? It gets set in the Action proto I think, at least for workflows. It doesn't look like we set it for remote bazel though.

[bduffany]

ah nvm I guess we do need this because it's how we disambiguate child invocations in the case of retries. Maybe @maggie-lou can take another look at this though because I think she added that linkage originally

[maggie-lou]

Rename to BUILDBUDDY_PARENT_RUN_ID?

[bduffany]

I think BUILDBUDDY_RUN_ID might be more consistent with the existing BUILDBUDDY_INVOCATION_ID ? since both are referring to the parent ci_runner run / invocation

[tylerwilliams]

That's what I was inspired by. Cool with either but I was trying to match what we ahve.

[maggie-lou]

This looks right to me. How will ninja emit this metadata to the BES?

The inner workflow job will look for this env var and if it's set will send it up in the build metadata. Does that seem ok?