| commit | 19ee1aad6d5e9a747e10acdfc29e6c10ef7e946a | [log] [tgz] |
|---|---|---|
| author | michajlo <michajlo@google.com> | Mon Aug 30 13:53:09 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Aug 30 13:54:22 2021 -0700 |
| tree | 8c57b7cac3d102ef3f7311d84648cd9080b46168 | |
| parent | 26354a06e4938208d704c0410fa34e104120f464 [diff] |
Remove Event's BUILD dependencies on filesystem things This winds up pulling in all sorts of dependencies (filesystem, profiler) for what's otherwise a low-level library. Also, this makes it much more clear that the whole withOutErr thing exists purely for ferrying action output around the system. Having events be semi-silently backed by files has been a source of several issues in the past, hopefully this rephrasing / indirection discourages future uses. I feel like the code in this area is still somewhat awkward - I tried to look past that for the most part and stay focused on cutting dependencies. PiperOrigin-RevId: 393846789
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
