| commit | 26ba23e465aad365138006b906431a865c5766cc | [log] [tgz] |
|---|---|---|
| author | Ittai Zeidman <ittaiz@gmail.com> | Thu Jul 14 14:28:19 2016 +0000 |
| committer | Yue Gan <yueg@google.com> | Thu Jul 14 17:45:55 2016 +0000 |
| tree | 1a094168ac61c2b0d47b11e707f2eb1857c28144 | |
| parent | aa0940a4de414dee547e4ce2e0a1e95c26393021 [diff] |
clarified needing to run generate_workspace from bazel source folder Hi, If you feel this is unnecessary please feel free to close this PR but it took me some time and @lberki's help to understand that even though I built the binary from source and I have the source cloned then I still need to run the command from the source folder so I added that note in. Closes #1489. -- Reviewed-on: https://github.com/bazelbuild/bazel/pull/1489 MOS_MIGRATED_REVID=127429574
{Fast, Correct} - Choose two
Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:
A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.
An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.
Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.
Find more background about Bazel in our FAQ.