-
Notifications
You must be signed in to change notification settings - Fork 282
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
When action StampWithIjar
runs it does not allow environment variables to be passed in using --action_env
#1232
Comments
@adam-singer do you need your scala imports to be stamped? If not can you disable it with a setting: If you don't need stamping, I would prefer to hold off from applying |
@liucijus let's say we don't ship this, long term what would be the solution or approach used? Based on some of the source code reading and commit logs, it seemed this feature was under development and forked a bit from the provided implementation in |
Can you send a PR with a |
We were able to get our code working by turning off stamping for scala_import, since ijar is no longer invoked. That said, I think @adam-singer has found |
@wisechengyi I'm testing out |
@liucijus |
### Description Originally it was unknown to me that we could use flags to directly disable the stamping of scala imports using `build --@io_bazel_rules_scala//scala/settings:stamp_scala_import=False` in the `.bazelrc` file. Discussion in bazelbuild#1232 cleared that up. ### Motivation Reverting #8 as it is not needed.
### Description Originally it was unknown to me that we could use flags to directly disable the stamping of scala imports using `build --@io_bazel_rules_scala//scala/settings:stamp_scala_import=False` in the `.bazelrc` file. Discussion in bazelbuild#1232 cleared that up. ### Motivation Reverting #8 as it is not needed.
### Description Originally it was unknown to me that we could use flags to directly disable the stamping of scala imports using `build --@io_bazel_rules_scala//scala/settings:stamp_scala_import=False` in the `.bazelrc` file. Discussion in bazelbuild#1232 cleared that up. ### Motivation Reverting #8 as it is not needed.
### Description Originally it was unknown to me that we could use flags to directly disable the stamping of scala imports using `build --@io_bazel_rules_scala//scala/settings:stamp_scala_import=False` in the `.bazelrc` file. Discussion in bazelbuild#1232 cleared that up. ### Motivation Reverting #8 as it is not needed.
When action
StampWithIjar
runs it does not allow environment variables to be passed in using--action_env
command line flag. This can lead to problems whenijar
is executed on systems that have compiled it with a tool chain picked up from the environment but not available on the host system in standard locations.A common solution applied is to allow durning action run
use_default_shell_env = True
as done in twitter-forks#8The text was updated successfully, but these errors were encountered: