| commit | e82beda0257958892ff8a15f3eae5c8f2f509118 | [log] [tgz] |
|---|---|---|
| author | Googler <messa@google.com> | Fri Jul 29 08:56:22 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jul 29 08:57:39 2022 -0700 |
| tree | 7535ebb449004ebe180aca36863c26a38d5b3756 | |
| parent | 7694cf75e6366b92e3905c2ad60234cda57627ee [diff] |
Expose actions fixed environment variables specified through feature configuration to Starlark Some fixed environment variables are added to the actions environment [like CppCompile action](https://github.com/bazelbuild/bazel/blob/master/src/main/java/com/google/devtools/build/lib/rules/cpp/CppCompileAction.java#L877) based on features configuration [code](https://github.com/bazelbuild/bazel/blob/master/src/main/java/com/google/devtools/build/lib/rules/cpp/CompileCommandLine.java#L66). These variables can be available in the analysis phase. This CL adds a flag `experimental_get_fixed_configured_action_env` to return these variables in `action.env`. This is needed to allow the use of aspects to output C++ actions information as a replacement for `print_action` command. Addresses: https://github.com/bazelbuild/bazel/issues/10376 PiperOrigin-RevId: 464088598 Change-Id: Id1c4e2badf5078d4d51f733aee8762411fd3b9ba
{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
