Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bazelisk has different PATH for workspace_status_command #471

Open
c-parsons opened this issue May 30, 2023 · 0 comments
Open

bazelisk has different PATH for workspace_status_command #471

c-parsons opened this issue May 30, 2023 · 0 comments
Labels
P2 We'll consider working on this in future. (Assignee optional) type:bug Something isn't working

Comments

@c-parsons
Copy link

My team's bazel setup involves invoking a script for --workspace_status_command (this flag is defined in our bazelrc).

The script in question invokes dirname, which is a common utility under /usr/bin.

This operates correctly using Bazel, because the PATH in the environment for our Bazel invocation includes /usr/bin.
When using bazelisk, this script fails because the env value of PATH in this invocation is only ~/.cache/bazelisk/downloads/bazelbuild/bazel-${commithash}-linux-x86_64/bin, which does not contain dirname.

@fweikert fweikert added type:bug Something isn't working P2 We'll consider working on this in future. (Assignee optional) labels Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants