commit | b23b8c778f2e077f1830f63b37083d9318324e5b | [log] [tgz] |
---|---|---|
author | adonovan <adonovan@google.com> | Thu Dec 12 11:42:14 2019 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Dec 12 11:43:13 2019 -0800 |
tree | 5f4c2d50c72de2b9c8225fea6d240d192c7a77a2 | |
parent | 26fbb9db59771c52b0e59da06841af1f4e14ee88 [diff] |
bazel syntax: delete SkylarkUtils The Phase is now recorded in lib.packages.BazelStarlarkContext. It is now always explicit whereas, before, failure to set it caused it to assume a default of ANALYSIS. In SkylarkRepositoryFunction, the "fetch" thread now uses phase=LOADING where before it has none (=ANALYSIS), which I suspect was an oversight. PiperOrigin-RevId: 285236359
{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