| commit | 55c97bcf9b99916a3fe59295be64c4aee860d823 | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Tue Dec 20 07:41:59 2016 +0000 |
| committer | Klaus Aehlig <aehlig@google.com> | Tue Dec 20 09:41:07 2016 +0000 |
| tree | f8ef267f8a1c0f86513aadf2d4bb1c30989bcdab | |
| parent | acbcbc2ff7dab2e68801c714e57475d6d57be8f2 [diff] |
Release script: if master branch does not exist, fall back on origin/master On ci.bazel.io local branch names are not set, so the release script was not finding information about the master branch. If the master ref does not exist, this change fall backs to looking at origin/master instead. Fixes #2263. To be cherry-picked for #2246. -- Change-Id: Ibe4f3533e529d79917233d89951f88cb58d14ce3 Reviewed-on: https://cr.bazel.build/8033 PiperOrigin-RevId: 142524954 MOS_MIGRATED_REVID=142524954
{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.