| commit | 96f48e917742e5be35b7a7f8aea927aa37a64740 | [log] [tgz] |
|---|---|---|
| author | Googler <michajlo@google.com> | Tue Oct 01 11:40:26 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Oct 01 11:42:15 2024 -0700 |
| tree | bb5366a91f2a018bef95a235edb811d3fadc3f43 | |
| parent | 924d5048dabbd33bbc4db7767beac36fc6201893 [diff] |
Add --run_in_client option to mobile-install This option allows the mobile-install deployer command to be sent to the bazel client for execution. This is useful for configurations where the bazel client is on a different machine than the bazel server. Takes the shortcut of having --run_in_client not respect --mobile_install_run_deployer. The latter (undocumented) flag exists as an earlier attempt at something like --run_in_client and AFAICT is only used for that purpose, so taking advantage of that situation to avoid introducing extra flags. We make these two flags get along after an internal compatibility window has passed. PiperOrigin-RevId: 681104164 Change-Id: Id462debabc54766b4b4f86024e4378f76798fd74
{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
