| commit | 2077c54069ed062587591a073ad0f03d521083e6 | [log] [tgz] |
|---|---|---|
| author | kshyanashree <109167932+kshyanashree@users.noreply.github.com> | Tue Aug 09 13:10:33 2022 -0700 |
| committer | GitHub <noreply@github.com> | Tue Aug 09 13:10:33 2022 -0700 |
| tree | 8b029ea583e8f4a6ac25bba85acf1a3e9692b9c1 | |
| parent | f440f8ec3f63e5d663e1f9d9614f05a39422102a [diff] |
Release 5.3.0 (#16074) * Updated Codeowners file (#16032) * Propagate the error message when a credential helper fails. (#16030) Closes #16012. PiperOrigin-RevId: 464732834 Change-Id: If51ce914098ff17ffe23fa4614947e7f4a5088dc Co-authored-by: Tiago Quelhas <tjgq@google.com> * Migrate legacy desugar wrapper to new rlocation() (#16025) RELNOTES: Fix for desugaring failure on Bazel+Android+Windows build scenario. PiperOrigin-RevId: 464654335 Change-Id: I845093b134dc68ae541603008fe7fee701c7451c Co-authored-by: Gowroji Sunil <48122892+sgowroji@users.noreply.github.com> * Correctly report errors thrown by CommandLinePathFactory#create. (#16036) This method is called while initializing the remote module [1]. Any exceptions not derived from java.io.IOException cause a silent server crash. [1] https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java;l=436;drc=f3211f00ae08746b5794ab01d404c32b43146aba Closes #16022. PiperOrigin-RevId: 464997904 Change-Id: I87fd5eaeb562d849bb830d68f1bfbbf06f6e0ea9 Co-authored-by: Tiago Quelhas <tjgq@google.com> * Fix an issue that `incompatible_remote_build_event_upload_respect_no_… (#16045) * Fix an issue that `incompatible_remote_build_event_upload_respect_no_… …cache` doesn't work with BwtB. The root cause is we use `Path` as key to check which files are omitted, but it also compares the underlying filesystem. When BwtB is enabled, the filesystem for the file is different so we failed to mark the file as omitted. This change fixes that by using `PathFragment` as key. Fixes #15527. Closes #16023. PiperOrigin-RevId: 465284879 Change-Id: I49bbd7a6055e0f234b4ac86a224886bd85797f71 * Update ByteStreamBuildEventArtifactUploader changes Removing the import as it is throwing the error Co-authored-by: Chi Wang <chiwang@google.com> Co-authored-by: Tiago Quelhas <tjgq@google.com> Co-authored-by: Ted <tedx@google.com> Co-authored-by: Gowroji Sunil <48122892+sgowroji@users.noreply.github.com> Co-authored-by: Chi Wang <chiwang@google.com>
{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
