| commit | 7aa5237a695cd725d7ddf9f2e47ddd48ce4ec95a | [log] [tgz] |
|---|---|---|
| author | pcloudy <pcloudy@google.com> | Tue Jan 11 05:03:54 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 11 05:05:02 2022 -0800 |
| tree | a03f022c86dd50900c35fa829f8db53da065f8cd | |
| parent | 2630f0e149222858d4c592599826d2e0f1ba39b3 [diff] |
Automated rollback of commit 73eaf24a7b290b1a5a47cb2e6c830f3ba10299a3. *** Reason for rollback *** This change is breaking too many downstream projects: https://github.com/bazelbuild/bazel/issues/14549 *** Original change description *** 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... *** PiperOrigin-RevId: 421002596
{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
