commit | 8d3f6cd3af7f40297815b8814555d504350a5a2a | [log] [tgz] |
---|---|---|
author | Googler <brandjon@google.com> | Thu Aug 03 08:32:43 2023 -0700 |
committer | fweikert <fwe@google.com> | Wed Aug 09 19:45:45 2023 +0200 |
tree | 7e2740c4bf93faea1854dbf9a91d543065979fdd | |
parent | 97852230306bb18531852528dce33348cf74c52b [diff] |
Automated rollback of commit 7a262a6ee88e0ecc10705c460e38efe32c8543e2. *** Reason for rollback *** Needed to rollback underlying https://github.com/bazelbuild/bazel/commit/3774f005792283b7ca6f2fa299a665f0c2ce459b *** Original change description *** Check for restricted Starlark syntax in REPO.bazel/MODULE.bazel files No `def`, `if`, etc. allowed. We extract the part of the NodeVisitor in PackageFactory that checks for this into a standalone RestrictedStarlarkSyntaxChecker class and clean up the interface (no need for the Consumer<SyntaxError> stuff if everyone already expects a SyntaxError.Exception for the compilation step anyway). PiperOrigin-RevId: 553485958 Change-Id: I40cf1aaf3235e781372e47f7a60ea6ab1ba9aecf
{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