| commit | ba4862d49333e9f50470b9d5a266ffd40c9cd2cc | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Fri May 03 06:13:23 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri May 03 06:14:33 2019 -0700 |
| tree | eaf35efdff6f2252c04739bb433a7f1504e753c0 | |
| parent | ac6b99932d6ea4546ed0cedc6ff686c42f12be8a [diff] |
Make files and directories under managed directories be correctly processed by SequencedSkyframeExecutor. TL;DR - two main changes: how to invalidate changed managed directories files, and how to force owning external repository to be evaluated before managed directories files. - In ExternalFilesHelper, introduce one more file type - EXTERNAL_REPO_IN_USER_DIRECTORY, for the files under managed directories. - For files under managed directories, require owning RepositoryDirectoryValue to be evaluated first. - For correct dirtying of files under managed directories, both with watchfs flag and without, the following should be taken into account: not only that new values for external repositories and managed directories files can not be injected at the stage of dirtying, but also files that used to be under managed directories on the previous evaluator invocation. The latter are still cached in evaluator, and the fact that they used to depend on their RepositoryDirectory values would prevent injection of the new values for them. To meet those conditions, in SequencedSkyframeExecutor.handleChangedFiles() filtering of the going-to-be-injected files is added. (The change can not be done inside ExternalDirtinessChecker only, as then it does not affect watchfs=true case). - ManagedDirectoriesBlackBoxTest added to demonstrate and validate the functionality of managed directories. PiperOrigin-RevId: 246496823
{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.