| commit | 9706dce2275f20743d241e662247e26fbc1acf80 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Tue Mar 07 06:48:20 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Mar 07 06:49:35 2023 -0800 |
| tree | e950487b6cb670d0a928a0499da8f91f6116e116 | |
| parent | 7f9a7b76c64481a38800be84467b9776be64e2b6 [diff] |
making --incompatible_use_platforms_repo_for_constraints do nothing. Using constraints from @bazel_tools//platforms with or without the flag will error out. Github: https://github.com/bazelbuild/bazel/issues/16330 RELNOTES: making --incompatible_use_platforms_repo_for_constraints do nothing. Using constraints from @bazel_tools//platforms with or without the flag will throw error with message "Constraints from @bazel_tools//platforms have been removed. Please use constraints from @platforms repository embedded in Bazel, or preferably declare dependency on https://github.com/bazelbuild/platforms" PiperOrigin-RevId: 514718831 Change-Id: I4c1c2a282c3770eb45f9325323c637485c9db9b7
{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
