| commit | df1706df3a30ec693ce0141206372b03bb9e7134 | [log] [tgz] |
|---|---|---|
| author | Googler <brandjon@google.com> | Thu Aug 03 09:28:26 2023 -0700 |
| committer | fweikert <fwe@google.com> | Wed Aug 09 19:45:45 2023 +0200 |
| tree | a883c004d90a77b591a830102fe552d93d4bdd8d | |
| parent | 8d3f6cd3af7f40297815b8814555d504350a5a2a [diff] |
Automated rollback of commit 3774f005792283b7ca6f2fa299a665f0c2ce459b. *** Reason for rollback *** Performance regression, b/294105788 *** Original change description *** Implement REPO.bazel - REPO.bazel is a new file at the root of repos that can only contain a `repo()` call with a bunch of package default arguments (similar to `package()`) - A new SkyFunction, RepoFileFunction, evaluates a REPO.bazel file and returns the `PackageArgs` object containing those arguments - PackageFunction for packages in repo `@foo` now depends on RepoFileFunction for `@foo` Fixes https://github.com/bazelbuild/bazel/issues/18077 PiperOrigin-RevId: 553500673 Change-Id: I866e73262ab75635c8927f8c77eb5412c01e16a9
{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
