| commit | 73eaf24a7b290b1a5a47cb2e6c830f3ba10299a3 | [log] [tgz] |
|---|---|---|
| author | Jiawen Chen <jiawen@gmail.com> | Mon Jan 10 04:12:09 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jan 10 04:13:42 2022 -0800 |
| tree | d2da5d75dd4ba8dc981767021a49184cde6489b7 | |
| parent | b92d5c3ca209ac3495b72fdf488eb9291455a8e2 [diff] |
Changes http_archive's netrc attr to a Label. This makes it possible to use a netrc file in another repository (e.g., the current repository) rather than referring to a netrc *file* inside the external repository (which usually does not make sense). Closes: 13662 RELNOTES[INC]: this incompatible change breaks old instances of http_archive that specified netrc as an absolute path. It is unlikely there are many instances in the wild since the path would refer to a netrc file inside the external repository by absolute path. Migration should be straightforward. Closes #14498. PiperOrigin-RevId: 420724049
{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
