| commit | 948323fd5b70c0b0d368c041fdc12aaa4c25ba28 | [log] [tgz] |
|---|---|---|
| author | Googler <ilist@google.com> | Fri Oct 18 04:44:58 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Oct 18 04:46:03 2024 -0700 |
| tree | 9e41e05c7cfe74c9e14ef9a1e0df62034cfdf675 | |
| parent | 49d7bb661296c6e494d502ee7c3ab43f3df17fe1 [diff] |
Fix shell tests not to assume MODULE.bazel is empty Removing this assumption makes it possible to put something into the default MODULE.bazel, generated by setup_module_dot_bazel. In my case, I'll use this to temporarily patch rules_java and protobuf so that they don't cause additional unnecessary downloads. Some tests assumed that MODULE.bazel was empty and deleted its content. Other tests needed empty MODULE.bazel, and assumed it already was. I believe this change is generally useful, when we need to do some patching. PiperOrigin-RevId: 687256923 Change-Id: Id0a5f25676c0ad8992737a37dfe9acaf573f1d35
{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
