| commit | fde4509e926af53df20db000d380d8fae486b587 | [log] [tgz] |
|---|---|---|
| author | Erik Kuefler <ekuefler@gmail.com> | Thu Sep 03 09:02:12 2015 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Thu Sep 03 09:05:14 2015 +0000 |
| tree | ab14eeed9312c31c376bb9eaa5c02361117a4400 | |
| parent | c010dc3d632a8ffd31619a7a2b88c00c3b4c6fb6 [diff] |
Fix a signed vs unsigned comparison warning in the ijar zipper. This is more than just a cosmetic issue. Since groovy and appengine rules depend directly on this target, the zipper gets built in the user's workspace whenever a groovy/appengine target is built. If the workspace is set to upgrade warnings to errors, this can cause builds to fail. -- Change-Id: I6c8b347df14098945c788411fc3e38f9c128596f Reviewed-on: https://bazel-review.googlesource.com/1951 MOS_MIGRATED_REVID=102223767
{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.