| commit | 8b0934795036154dd4d835ea30770bc0b86243a9 | [log] [tgz] |
|---|---|---|
| author | janakr <janakr@google.com> | Tue Jan 16 14:15:09 2018 -0800 |
| committer | Copybara-Service <copybara-piper@google.com> | Tue Jan 16 14:23:31 2018 -0800 |
| tree | 1ca728b45ef0898299ec0562ab53887091bb5768 | |
| parent | 53e45318ad8da0a244639a44c1c9a1720d8c4b10 [diff] |
Remove mtime field from FileStateValue. We stopped treating empty files specially in the execution phase after unknown commit. So this code is mostly if not entirely orphaned. The only scenario in which this would lead to a semantic difference that I can think of is if the user is running with --nouse_action_cache and a running Bazel server, and they have an action they want to re-run when an empty input file changes, which isn't something we need to be concerned about. PiperOrigin-RevId: 182109952
{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.