| commit | 40d8f92267c3fc1bd1ab402d22d2f892b3d5b884 | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Fri Dec 02 14:58:56 2016 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Fri Dec 02 19:08:32 2016 +0000 |
| tree | a78f5f5fc1e4c123af517883599700b88c966d5c | |
| parent | 0d35261db8d4ddc43b770d5228bfd74813ad6f5f [diff] |
Release: split up the create operation Now the create operation is really two part: 1. Overwrite the branch with new cherry-picks 2. Create the commit from the history The second part will be provided as a command. -- Change-Id: Id527fa00c0d573825fcb5f324516cfdd4dcb9139 Reviewed-on: https://cr.bazel.build/7350 PiperOrigin-RevId: 140845679 MOS_MIGRATED_REVID=140845679
{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.