-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Allow options to use ~ or $HOME #2054
Labels
category: misc > misc
P3
We're not considering working on this, but happy to review a PR. (No assignee)
type: feature request
Milestone
Comments
this (in combination with #1752) sounds valuable since it lowers the entry costs of an organization. People can check out and best practices are laid out in the shared bazelrc |
+1 |
davido
added a commit
to davido/bazel
that referenced
this issue
Mar 14, 2018
Fixes bazelbuild#2054. Allow users to be able to specify user specific paths. With this option we can now commit bazel configuration file and force local action cache activation per default: $ cat tools/bazel.rc build --experimental_local_disk_cache_path=~/.gerrit/bazel-cache/cas build --experimental_local_disk_cache build --experimental_strict_action_env Test Plan: $ bazel test //src/test/java/com/google/devtools/build/lib:util_test
davido
added a commit
to davido/bazel
that referenced
this issue
Mar 19, 2018
Fixes bazelbuild#2054. Allow users to be able to specify user specific paths. With this option we can now commit bazel configuration file and force local action cache activation per default: $ cat tools/bazel.rc build --experimental_local_disk_cache_path=~/.gerrit/bazel-cache/cas build --experimental_local_disk_cache build --experimental_strict_action_env Test Plan: $ bazel test //src/test/java/com/google/devtools/build/lib:util_test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
category: misc > misc
P3
We're not considering working on this, but happy to review a PR. (No assignee)
type: feature request
It would be nice for users to be able to specify user-specific paths. We'd probably have to add support for both client & server path parsing.
See #1752 (comment) for context.
The text was updated successfully, but these errors were encountered: