| commit | a3b8e314992085203307f8de4d97f325a3274ba9 | [log] [tgz] |
|---|---|---|
| author | Googler <cushon@google.com> | Tue Oct 08 10:21:38 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Oct 08 10:23:19 2024 -0700 |
| tree | 46fabf72d7268962950d6cbb65ef92155bd85583 | |
| parent | 233a29cddaf82c84f6ea806482363bc3d45f36ce [diff] |
Automated rollback of commit d2f19710b574a76206c7499d746e7c9f7e733e99. *** Reason for rollback *** This regressed support for non-ASCII characters in paths on systems that don't support C.UTF-8, see b/372094587 *** Original change description *** Use `C.UTF-8` instead of `en_US.UTF-8` locale for Java compilation `C.UTF-8` is now the universally accepted standard UTF-8 locale, to the point where some minimal distributions no longer ship with `en_US.UTF-8` (e.g. RHEL 9 with `glibc-minimal`). CentOS 7, the only major distribution that doesn't have the locale, is EOL now. Note that the locale can't be detected automatically since the action may run on a machine that isn't the host.... *** PiperOrigin-RevId: 683672854 Change-Id: I6c1d4fe43066c068db345987f54388c6fcdd0539
{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
