| commit | 52d1d4ae9bfee7379093d46258fa3a56e4d69e61 | [log] [tgz] |
|---|---|---|
| author | twigg <twigg@google.com> | Thu Mar 10 16:41:11 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 10 16:43:58 2022 -0800 |
| tree | 851498a64ccb686ed6593da0bf8ce65cc3f312b2 | |
| parent | 50dc4463b8daeceb01403c3390532a8953ce24bc [diff] |
Add `--experimental_output_directory_naming_scheme` with two modes. The `legacy` mode retains pre-existing behavior for determining the ST hash value by tracking an `affected by starlark transition` list and consuming it. The new `diff_against_baseline` mode determines the ST hash value by diffing the current configuration against the build's baseline configuration (currently, the configuration used to prime all top-level targets). Note that this mode specifically turns off tracking the `affected by starlark transition` for performance reasons (see linked bug for details). Related github issue: https://github.com/bazelbuild/bazel/issues/14023 PiperOrigin-RevId: 433882310
{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
