| commit | 3caa2b2425172c1515c6df0a34c188987be7aa11 | [log] [tgz] |
|---|---|---|
| author | Peter Schmitt <schmitt@google.com> | Thu Oct 08 14:59:04 2015 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Fri Oct 09 14:39:59 2015 +0000 |
| tree | 16307c0eae9f99ada60e01cfdb4d77ec2aaf95b3 | |
| parent | c97ee9c33285b36926ed560e4c089b6bc28f4a25 [diff] |
Allow use of signing certificate name for iOS app signing. The value of new flag --ios_signing_cert_name takes precedence over any specified provisioning profilefor purposes of signing. RELNOTES: --ios_signing_cert_name allows specifying a cert for iOS app signing -- MOS_MIGRATED_REVID=104961817
{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.