| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
| |
Improvement for #424.
--
MOS_MIGRATED_REVID=102566748
|
|
|
|
|
|
|
| |
mount the individual files.
--
MOS_MIGRATED_REVID=102142064
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102050490
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101572272
|
|
|
|
|
|
|
| |
--
Change-Id: I4e65cc583e758d2f7e45209ffcb37f6a871e2ed7
Reviewed-on: https://bazel-review.git.corp.google.com/#/c/1840
MOS_MIGRATED_REVID=101462155
|
|
|
|
|
|
|
|
|
| |
is Linux, do real auto-detection whether it is supported on the host or not and enable / disable it based on the result.
The warning that is printed when the Linux kernel is too old to support sandboxing can be disabled via a flag.
--
MOS_MIGRATED_REVID=101461120
|
|
|
|
|
|
|
| |
syscall.
--
MOS_MIGRATED_REVID=101458944
|
|
|
|
|
|
|
|
|
|
|
|
| |
use non-declared inputs) and safety (spawns can no longer affect the host system, e.g. accidentally wipe your home directory). This implementation works on Linux only and uses Linux containers ("namespaces").
The strategy works with all actions that Bazel supports (C++ / Java compilation, genrules, test execution, Skylark-based rules, ...) and in tests, Bazel could successfully bootstrap itself and pass the whole test suite using sandboxed execution.
This is not the default behavior yet, but can be activated explicitly by using:
bazel build --genrule_strategy=sandboxed --spawn_strategy=sandboxed //my:stuff
--
MOS_MIGRATED_REVID=101457297
|
|
|
|
|
|
|
| |
fix the Skylark rules and tests that so far failed to declare dependencies on the JVM.
--
MOS_MIGRATED_REVID=101215495
|
|
|
|
|
|
|
|
| |
Removing them would break people that have their tools folder checked in
their workspace.
--
MOS_MIGRATED_REVID=96392423
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=96365813
|
|
|
|
|
|
|
|
|
|
|
| |
resource, then passing it to the parser as a string instead of putting it into embedded_binaries then passing a Path to it to the parser.
This makes the upcoming default WORKSPACE rules for Android much more palatable. In particular, Android rules won't need to be special cased when building the Bazel binary because the contents are self-contained in BazelRuleClassProvider (and the jdk.WORKSPACE file, which is a simple Java resource)
Even better would be not to use a string, but some kind of structured data, but that's probably more effort than it's worth.
--
MOS_MIGRATED_REVID=95983199
|
|
|
|
|
|
|
|
|
|
| |
Skylark rules now depends completely on the external repository
to access the JDK tooling.
--
Change-Id: I48d461524d63d556bcd4af49f6ba2aecf1ed7068
Reviewed-on: https://bazel-review.googlesource.com/#/c/1500/
MOS_MIGRATED_REVID=95720688
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Generate a srcjar artifact, and use native.java_library to emit the
actual jar file.
Post-review modifications:
- Formatted genproto.bzl
- Use //external:jar instead of relying on PATH
- Make proto library a java_import instead of a filegroup in
test setup.
--
Change-Id: I005f801f09439bbca43e483ad4a47da4588fea94
Reviewed-on: https://bazel-review.googlesource.com/1362
MOS_MIGRATED_REVID=94914935
|
|
|
|
|
|
|
|
|
| |
eg. on the command line.
--
Change-Id: I888dbe55d0e89de581a7180a3b85775e85e1e476
Reviewed-on: https://bazel-review.googlesource.com/#/c/1361
MOS_MIGRATED_REVID=94279633
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=94131018
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The -extdirs flag sets a search path to the directory containing the JDK's
extension classes, and should always be set explicitly when cross-compiling. If
it is unset, the ext directory of the host JDK will be used instead.
javac requires that -extdirs be a list of directories. The blaze --javac_extdir
flag takes the label of a filegroup with the 'path' attribute set, and passes
the directory path through to JavaBuilder.
--
MOS_MIGRATED_REVID=94001278
|
|
|
|
|
|
|
|
| |
The main method was too big for easy understanding of the various step.
This split put the various step into specific method.
--
MOS_MIGRATED_REVID=93886113
|
|
|
|
|
|
|
| |
Also use getopt for option parsing.
--
MOS_MIGRATED_REVID=93881222
|
|
|
|
|
|
|
|
|
|
|
| |
This remove the operation not permitted when trying to write
the gid mapping. The error message was the result of a change
in Linux 3.19 to address a security issue. Further explanation
can be found in the source example of
http://man7.org/linux/man-pages/man7/user_namespaces.7.html.
--
MOS_MIGRATED_REVID=93870786
|
|
|
|
|
|
|
|
| |
The root of the sandbox is specified using the -S flag whereas the first
line of the program was specifying -R.
--
MOS_MIGRATED_REVID=93869647
|
|
|
|
|
|
|
| |
This factors the various call to open/snprintf/write/close.
--
MOS_MIGRATED_REVID=93865956
|
|
|
|
|
|
|
| |
/bin/bash clobbers euid with uid, which is undesirable when process-wrapper is a setuid binary being used for isolation.
--
MOS_MIGRATED_REVID=93051178
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=88742425
|
|
|
|
|
|
|
| |
This is needed for taking the runfiles prefix from the WORKSPACE file instead of hardcoding it.
--
MOS_MIGRATED_REVID=87347883
|
|
|
|
|
|
|
| |
Doesn't do anything yet, but you can refer to //tools/jdk:jdk as //external:jdk.
--
MOS_MIGRATED_REVID=86087956
|
|
--
MOE_MIGRATED_REVID=85702957
|