| commit | a3990cc2d48704e4cdf35b6600cdfe4aae3a148f | [log] [tgz] |
|---|---|---|
| author | Googler <philomath@google.com> | Tue Aug 16 09:24:38 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Aug 16 09:25:38 2022 -0700 |
| tree | 7f13656edea234631619a09d988863b5e7f99a0a | |
| parent | 3697ca55b04ce308d8afcfeeee6bbea14ff9dbb4 [diff] |
Site update to fit new information architecture per[] Step 4. in [InfoArch roadmap](https://www.google.com/url?q=https://docs.google.com/document/d/1NAeZ61LDPS0DEhbD-tXjs7rcxKgEbq0aGsEm1PQi3Qk/edit%23bookmark%3Did.2anx0cdbkeop&sa=D&source=calendar&ust=1660607278459403&usg=AOvVaw3hud4V-P5BLeNeYk1zPS58) * Refactored site map * Combined updating-bazel.md into bazelisk.md * Deduped and deleted /start/getting-started.md * Deleted Choose a version index.md * Deduped and deleted /contribute/getting-started.md into /contribute/contributor-guide.md * Fixed left nav link for java.md * Fixed Nav on FAQ page * Set up redirects for deleted/combined/ moved pages TODO: * TODOs in notes in[] * Consider saving copy from /contribute/getting-started.md for First Build tutorials/ quickstart guide * Make CTO pitch the About Bazel landing page * Fix landing pages PiperOrigin-RevId: 467944041 Change-Id: I64d6f35cbbf84b3280f001467081cb42cc039ed0
{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:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
