commit | 485eb969bbfbfbeb7d9501fa2b8f4e6ac5aa7da7 | [log] [tgz] |
---|---|---|
author | Lukacs Berki <lberki@google.com> | Wed Jan 13 10:47:29 2016 +0000 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Wed Jan 13 13:19:28 2016 +0000 |
tree | 18996457a94174100b600cf95223ae9385d7015b | |
parent | 0e396b827bca5ee507aadc875169e47d959a7136 [diff] |
Make package names in the package_group.packages attribute refer to the repository where the package group is. There is currently no way to refer to packages in other repositories and that doesn't seem to be useful, because visibility currently checks the repository name in the label and that can be changed in the main WORKSPACE file. If needed, it'd be pretty easy to implement, though. As a drive-by fix, made the parsing of the package name call into the same logic implemented in the cmdline package because code duplication is bad, mmmkay? Fixes #767. -- MOS_MIGRATED_REVID=112032508
{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.