commit | 0e8de273177fd3d29d3d7627c3cb0310f8ac1205 | [log] [tgz] |
---|---|---|
author | Tiago Quelhas <tjgq@google.com> | Wed Dec 07 01:56:46 2022 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Dec 07 01:58:10 2022 -0800 |
tree | 112144bbbad846b6581d28f80eae776698fdbb2f | |
parent | 47c93b7e38cf9498617777fcb28928179e7f9013 [diff] |
Remove dead code in embedded_tools.bzl. The embedded_tools rule was introduced in https://cr.bazel.build/13250, but seems to have never been used. I can't tell whether the intention was to use it in a followup CL, or if it was just left over by mistake. Closes #16925. PiperOrigin-RevId: 493539978 Change-Id: Ie8ebfda2bc80677e3a1358280212fdbd296d9fe5
{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