| # [Bazel](https://bazel.build) |
| |
| *{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. |
| |
| ## Getting Started |
| |
| * [Install Bazel](https://docs.bazel.build/install.html) |
| * [Get started with Bazel](https://docs.bazel.build/getting-started.html) |
| * Follow our tutorials: |
| |
| - [Build C++](https://docs.bazel.build/tutorial/cpp.html) |
| - [Build Java](https://docs.bazel.build/tutorial/java.html) |
| - [Android](https://docs.bazel.build/tutorial/android-app.html) |
| - [iOS](https://docs.bazel.build/tutorial/ios-app.html) |
| |
| ## Documentation |
| |
| * [Bazel command line](https://docs.bazel.build/user-manual.html) |
| * [Rule reference](https://docs.bazel.build/be/overview.html) |
| * [Use the query command](https://docs.bazel.build/query.html) |
| * [Extend Bazel](https://docs.bazel.build/skylark/concepts.html) |
| * [Write tests](https://docs.bazel.build/test-encyclopedia.html) |
| * [Roadmap](https://bazel.build/roadmap.html) |
| * [Who is using Bazel?](https://github.com/bazelbuild/bazel/wiki/Bazel-Users) |
| |
| ## Reporting a Vulnerability |
| |
| 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. |
| |
| ## Contributing to Bazel |
| |
| See [CONTRIBUTING.md](CONTRIBUTING.md) |
| |
| [](https://ci.bazel.build) |
