| commit | 9d9657b089bde11071d558e65f4b3b87d8a765d3 | [log] [tgz] |
|---|---|---|
| author | Philipp Wollermann <philwo@google.com> | Fri Aug 19 10:45:28 2016 +0000 |
| committer | Philipp Wollermann <philwo@google.com> | Fri Aug 19 10:47:46 2016 +0000 |
| tree | 3739f270d0e24f30d3c2a6d59ac5bc7cd93ccc26 | |
| parent | f9fa99d0c1a25d0f7c2753043c5f88cce2cac255 [diff] |
Fix Bazel CI by appending the newline to WORKSPACE, which got lost in commit bfaff29b1bafd7892a2197b7cf826e1be0ff3927. Without the newline, our bazel/scripts/ci/build.sh will append an android_sdk_repository() rule into the file in such a way, that it produces a syntax error. Also fix the build.sh script to be more resilient and not actually require the newline. -- MOS_MIGRATED_REVID=130737331
{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.