| commit | 67134c8e5bf56b8ed0edba42a251ae34b64f8d16 | [log] [tgz] |
|---|---|---|
| author | Kristina Chodorow <kchodorow@google.com> | Wed Jul 27 16:34:27 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Thu Jul 28 09:14:49 2016 +0000 |
| tree | 687d94cc45c28f083fc3d58608dd2ba4f6c9811d | |
| parent | 4e1ced48f6f2ed37aa835d562b6539cc933922de [diff] |
Rename some PackageId and RepositoryName fields/methods in prep for deep execroot change This is in prep for making the execution root path for external repositories ../repo_name (instead of external/repo_name). Right now, the getRunfilesPath() returns that path, so that is renamed getExecRoot() (since the runfiles are really just a reflection of the execRoot structure). getSourceRoot() replaces getPathFragment, which has always been a confusing name (it's not clear from the name what the difference is between it and getPackageFragment()). It returns the relative path to source files for external repositories (external/repo_name). Also renamed/moved to more sensible class a few static RepositoryName fields. -- MOS_MIGRATED_REVID=128594419
{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.