| commit | 9f2542f91e99b40de65506c8f4768ec0003a4e5d | [log] [tgz] |
|---|---|---|
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | Tue Aug 16 08:29:35 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Aug 16 08:30:55 2022 -0700 |
| tree | e13d842bc52cd9561225bd94fc24aac76cec4112 | |
| parent | 41f7f8aa9a7cc714fe5f12a346b91e04ec9d7561 [diff] |
Preserve relative order of explicit and expanded Starlark flags Previously, Starlark flags expanded from a --config stanze would always be added to the end of the residue containing the explicitly given Starlark flags. As a result, Starlark flags expanded from --config could not be overridden. With this commit, Starlark flags are parsed with the same semantics as a regular allowMultiple option, thus preserving their order through expansions. This is implemented by introducing a synthetic allowMultiple option of type List<String> in OptionsParserImpl that skipped args are parsed into. As a result, Starlark options are now available from the new getSkippedArgs() method on OptionsParser rather than as part of the residue, with the latter now only containing build targets. Fixes #13231 Fixes #15679 Closes #15807. PiperOrigin-RevId: 467931815 Change-Id: Ic64c6e075c08d898e5e7b8bf4c777827134d89fa
{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
