| commit | 3916df650614e05b83f77f18cc2ec80bea1fc189 | [log] [tgz] |
|---|---|---|
| author | Googler <michajlo@google.com> | Wed Jun 15 06:04:05 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jun 15 06:05:09 2022 -0700 |
| tree | 2dff0ae91b47acba43de41580bd4a31c285ec129 | |
| parent | dd57d4139ca2f10932fd6067c027be7744a1b083 [diff] |
Make options parsing in BlazeRuntimeWrapper more realistic Actually select the options for the command and apply the command-specific invocation policy. Previously everything was considered "build" and the command passed to the invocation policy was "null", which is not what happens in production code. Making this work also required registering commands so that the invocation policy's command-inheritance logic actually worked. The list of commands isn't exhaustive, but should do the trick, easy enough to add more as we need them (I don't think we need _all_ the commands for now at least). There's still plenty to clean up around options handling in RuntimeWrapper et al - for example we should be able to pluck options classes from the registered modules instead of explicitly providing them, but that's for another change. PiperOrigin-RevId: 455110823 Change-Id: I6223f7508c785e52a160ff41739b704da5354b12
{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
