| commit | a0e779bbee8d0e135b8ab18b9aa6eee2cb5f09a6 | [log] [tgz] |
|---|---|---|
| author | Googler <jhorvitz@google.com> | Fri Mar 10 12:35:30 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Mar 10 12:36:46 2023 -0800 |
| tree | a8cf1ee6ebb0d0b5c308621fd29b2856429ff455 | |
| parent | 082e5bb6cf74b1d0dafbd658da928d4baa2c243e [diff] |
Use empty collections instead of `null` for `outputSymlinks` and `discoveredModules` in `ActionExecutionValue`. There are no places where callers need to distinguish `null` from empty. For output symlinks, `ActionInputMapHelper` already checks `Artifact#isFileset`. For discovered modules, `CppCompileAction` already checks `module.isFileType(CppFileTypes.CPP_MODULE)`. Both of these checks guarantee that the values are non-null currently. `createForTesting` is removed from `ActionExecutionValue`. It is replaced with convenience methods in `ActionsTestUtil`. The convenience methods are used everywhere except tests for `ActionExecutionValue` itself. Also fix various code warnings. PiperOrigin-RevId: 515710662 Change-Id: I72fdc388d2247527f870aa4bd5620e8928507f8f
{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
