| commit | c44ee628c698358e11e4918ba394e74e6dfba3c7 | [log] [tgz] |
|---|---|---|
| author | laurentlb <laurentlb@google.com> | Wed May 13 11:36:53 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed May 13 11:38:05 2020 -0700 |
| tree | 6151c574fbfb4d927c846dcb5920b355398b3d35 | |
| parent | 5c8a5f55b9bd2455ed6392f5f334a3b4669199e4 [diff] |
Move documentation of 'visibility' to a separate page Visibility is a core concept (you have to know about when you create a 2nd package). It shouldn't be hidden in a table, inside the list of common attributes. I also plan to expand the documentation. Creating a proper section for visibility will leave more space for structuring the content. This change doesn't modify the content itself (except for one introduction sentence). https://github.com/bazelbuild/bazel/issues/8982 RELNOTES: None. PiperOrigin-RevId: 311371192
{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
