Closed Place1 closed 1 year ago
Interesting, we hadn't hit this case because we don't have any multiruns in the root BUILD file in our project, so our paths end up being tools/whatever/foo.bash
which solves this. I think doing either ./
or computing the absolute path with os.path.abspath(command.path)
would solve this. I'm not sure which is better, I guess doing ./
, want to submit that as a PR?
Thanks for replying @keith i've put up a PR. This change allows my workspace to use the multirun as expected.
Surprisingly the tests still pass with this change. I'm not sure how to add a test for this. Perhaps you can help me with that?
Sorry I didn't see that until I had merged your PR. Submitted this: https://github.com/keith/rules_multirun/pull/21
Hello, i'm trying to use multirun for a similar use-case discussed here: https://github.com/bazel-contrib/rules_oci/issues/248#issuecomment-1558154145
I've got the following rules:
I've found that running
bazel run :push
orbazel run :push_command
works as expected but i'm having trouble withbazel run :push_multi
I've attempted to debug by adding a
print(os.getcwd())
to the multirun.py script to check if thepush_command.bash
script exists and it does.If I edit the
multirun.py
script so that it executes./push_command.bash
instead then it works. The./
prefix may be needed?