[8.7.0] Allow --test_env / env= to override coverage env (#29383) Bazel sets some environment variables for CC coverage collection that can be useful to override in some projects. Previously this was possible but as a side effect of 87b0a1f202992ac98f73bc230551b6166c313a06 it stopped working. This re-enables that and covers it in tests Fixes https://github.com/bazelbuild/bazel/issues/23247 Closes #29110. Fixes https://github.com/bazelbuild/bazel/issues/29167 PiperOrigin-RevId: 892333567 Change-Id: If5dd77b1cc98390622276865ee80772fdbcb216c (cherry picked from commit 15e078b9361333091df54e4f57fed88b7c4cd5bd)
{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
