| commit | 505596a45461c0e7a212c30f10db86e1e53d483b | [log] [tgz] |
|---|---|---|
| author | Tony Aiuto <aiuto@google.com> | Thu Oct 17 11:11:11 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Oct 17 11:13:02 2024 -0700 |
| tree | f92036d21664f2378a8d8cfd59d9914332279cde | |
| parent | 2b9a2e79d57fbae57337f2afdabb44bdad7d33f4 [diff] |
Remove dependency on python six from bazel_external_repository_test The external repository test depends on a .tgz file which would be downloaded from another repo. I think that when whomever made the original test, they just copied six-1.0.0.tar.gz to the test data. But the test does not actually care about what the repo does. It only cares that it can unload it and inject a BUILD file. This PR replaces that tarball with a trivial equivalent. This does not impact the bazel distribution size, it just means we have one less false dependency. Fixes: #18272 Closes #23875. PiperOrigin-RevId: 686978582 Change-Id: Id59be40caa6625e6bd39d36cef108ee15b3a8d9e
{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
