commit | 342f2244b4e47a8680ef71f2650c9aaede839641 | [log] [tgz] |
---|---|---|
author | Googler <lberki@google.com> | Tue Feb 06 02:34:13 2024 -0800 |
committer | fweikert <fwe@google.com> | Wed Feb 14 18:24:05 2024 +0100 |
tree | 01cf2b3387aee380904bc16feece090b45ca556f | |
parent | cc8be0ab496570eb155ba220012f52f6a6c7082d [diff] |
Do not build the runfiles tree when creating deploy jars. I missed this from https://github.com/bazelbuild/bazel/commit/6a4d61ebf2dc2214ffe6abc807e4f597175e1a6c and as it is, Bazel at HEAD builds the runfiles tree, but not the artifacts in it, thus resulting in the runfiles tree being made of broken symlinks. RELNOTES: None. PiperOrigin-RevId: 604583234 Change-Id: I5d106719c269a4b145a5f43ded0de749f55da3b0
{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