| commit | 74e928bbda0744d12a1b871d41782d8445cee9db | [log] [tgz] |
|---|---|---|
| author | bazel.build machine account <15028808+bazel-io@users.noreply.github.com> | Wed Feb 21 13:01:19 2024 -0500 |
| committer | GitHub <noreply@github.com> | Wed Feb 21 18:01:19 2024 +0000 |
| tree | cc147c2e5028d5f333820716745ae3c2f1a813de | |
| parent | a109d5c8ee55138d858c994c26e0e82435e40ca8 [diff] |
[7.1.0] Do not record any repo mapping entries in the RepoMappingRecorder for WORKSPACE repo rules (#21457) Follow-up to https://github.com/bazelbuild/bazel/commit/1cbf09dd45a4bb4cc73ace58ae344bb90e709752; beyond not recording those entries in the marker file, we shouldn't even record them in memory in the first place. This avoids nasty problems with unexported repo rules (gah) and should be an extremely tiny performance win as a bonus... Fixes https://github.com/bazelbuild/bazel/issues/21451 Commit https://github.com/bazelbuild/bazel/commit/e84d0533f93889772820084627659a5324e1942c PiperOrigin-RevId: 609010175 Change-Id: I90eb921b09068f327b42886ea0a1875374a94049 Co-authored-by: Googler <wyv@google.com>
{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
