Skip to content

Enable use_default_shell_env everywhere#1114

Merged
keith merged 2 commits intomasterfrom
ks/enable-use_default_shell_env-everywhere
Sep 19, 2023
Merged

Enable use_default_shell_env everywhere#1114
keith merged 2 commits intomasterfrom
ks/enable-use_default_shell_env-everywhere

Conversation

@keith
Copy link
Copy Markdown
Member

@keith keith commented Sep 19, 2023

Now that bazel 7.x has
https://bazel.build/reference/command-line-reference#flag--incompatible_merge_fixed_and_default_shell_env
enabled by default, we can set use_default_shell_env = True moving
forward. This makes actions respect --action_env=FOO which can be
useful for things like TOOLCHAINS, ZERO_AR_DATE, TMPDIR, etc.
Previously these were ignored.

Now that bazel 7.x has
https://bazel.build/reference/command-line-reference#flag--incompatible_merge_fixed_and_default_shell_env
enabled by default, we can set `use_default_shell_env = True` moving
forward. This makes actions respect `--action_env=FOO` which can be
useful for things like `TOOLCHAINS`, `ZERO_AR_DATE`, `TMPDIR`, etc.
Previously these were ignored.
@keith keith merged commit 8c09041 into master Sep 19, 2023
@keith keith deleted the ks/enable-use_default_shell_env-everywhere branch September 19, 2023 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants