| commit | 39c00d20e89395d7bb126ba6c3bba10a7214e1ad | [log] [tgz] |
|---|---|---|
| author | steinman <steinman@google.com> | Fri Mar 20 15:23:10 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Mar 20 15:24:24 2020 -0700 |
| tree | 296d21bd2ce52d017807c2b661e97e467f20502e | |
| parent | ebb86fcdc202c440a362a54f6b0de8a049dfa84b [diff] |
Validate build artifacts that originated remotely and can't be accessed locally, unless otherwise specified by the OutputService. Previously, we assumed that if a file wasn't available locally and we know it was available remotely recently, the file is still accessible, but this isn't true when you've written a file to a remote OutputService and then switch to a local (or no) OutputService. This results in build failures when Bazel tries to read a file that it no longer can access that it should have validated during the analysis phase. PiperOrigin-RevId: 302110160
{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:
See CONTRIBUTING.md
