| commit | 7b3804a33cbaec4b653599680749fe3e5b51ec36 | [log] [tgz] |
|---|---|---|
| author | gregce <gregce@google.com> | Tue May 21 07:01:44 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue May 21 07:03:00 2019 -0700 |
| tree | 74a229c85aad23e29190699e06790013114e632b | |
| parent | 140c04bbaf0d07eb88abd1e40c1ee4f79cc84c57 [diff] |
Add --experimental_output_paths=content (without implementation) This will enable content-based output paths, as described at https://docs.google.com/document/d/17snvmic26-QdGuwVw55Gl0oOufw9sCVuOAvHqGZJFr4/edit#heading=h.5mcn15i0e1ch. See https://github.com/bazelbuild/bazel/issues/8339. Notes: * I originally tried to put this in BuildRequestOptions since this goes beyond configuration (it also affects execution-phase logic). But piping that to the right consumers was a lot more awkward, so here it is. * One nice thing about keeping this in BuildConfiguration is switching it automatically invalidates configured targets without having to pass external Skyframe context. * This should arguably be a startup option since it's effect on action caches, the general build graph, action execution logic, and output metadata services could be potentially far-reaching. I wouldn't particularly call this a flag where it's safe to keep all Bazel's incremental state when switching. But I'm trying to avoid use of startup options and we might be able to get away just fine with with judicious use of reset() calls to things like SkyframeBuildView. For the current super-experimental alpha phase I think these risks are worth the ease-of-use putting this in BuildConfiguration offers. PiperOrigin-RevId: 249241985
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds 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:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.