bazelbuild/bazel
GitHub で見るSystem-specific environment variables on Windows pollute remote cache
Open
#3,500 opened on 2017年8月3日
P4help wantedteam-Remote-Exectype: bug
Repository metrics
- Stars
- (25,384 stars)
- PR merge metrics
- (平均マージ 22d 20h) (30d で 77 merged PRs)
説明
Description of the problem / feature request / question:
When building C++ rules on Windows with MSVC, system-specific environment variables are part of the inputs, i.e.
SET TEMP=C:\Users\<my_user>\AppData\Local\Temp
SET TMP=C:\Users\<my_user>\AppData\Local\Temp
SET PATH="...;C:\Program Files (x86)\Skype\Phone\;C:\Program Files (x86)\Bitvise SSH Client;..."
For remote caching, this prevents sharing outputs between different systems.
Environment info
-
Operating System: Windows 10
-
Bazel version (output of
bazel info release): release 0.5.4rc1
Have you found anything relevant by searching the web?
https://groups.google.com/forum/#!topic/bazel-discuss/4GV8lJzfeGQ