bazel-skylib/rules/private
Alexandre Rostovtsev 908bf1431d
Allow sandboxing for copy_* and fix copy_directory tests (#392)
After some thought, I have to say that forcing a local strategy for
copy_file/copy_directory is inappropriate. The point of a sandbox is to
catch hermeticity bugs; disabling the sandbox may be useful for
performance, but it's up to the user to do it if they trust us - and
they can do it via flag. The default should be paranoia and safety.

And on the subject of strategies - using a genrule to create an empty
directory fails in environments where genrules run remote by default
(and thus, copy_directory tests fail). We could, of course, set local=1,
but that disables the sandbox and causes scary warnings. Instead, add a
proper empty_directory rule to test with.
2022-09-02 10:42:43 -04:00
..
BUILD Use stricter execution requirements for copy actions (#372) 2022-06-10 16:23:43 +02:00
copy_common.bzl Allow sandboxing for copy_* and fix copy_directory tests (#392) 2022-09-02 10:42:43 -04:00
copy_directory_private.bzl Use stricter execution requirements for copy actions (#372) 2022-06-10 16:23:43 +02:00
copy_file_private.bzl Use stricter execution requirements for copy actions (#372) 2022-06-10 16:23:43 +02:00
maprule_util.bzl maprule: move functionality to maprule_util.bzl (#132) 2019-03-25 16:48:50 +01:00
write_file_private.bzl copy_file: Do not add non-executables to default_runfiles (#326) 2022-05-16 17:27:25 -04:00