| commit | cc784073ca363ea25b3ee1a51c4a060ea2f5f081 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Mon Oct 10 23:16:02 2016 +0000 |
| committer | Yue Gan <yueg@google.com> | Tue Oct 11 08:45:59 2016 +0000 |
| tree | e468442b8a95ad04da537deaa81e8aa95712501c | |
| parent | a725afe0644b0a6fe179e10e8c56ed3eedb81de5 [diff] |
Rollback of commit 51417759a37e5b11003dd773d5c90ddd4c7a6aa7. *** Reason for rollback *** This CL is causing failures in one of our integration tests: //javatests/com/google/security/authorization/sphinx/integration:SimpleUIEditorPageE2eTest_firefox-linux [] link: [] Note: Specifically, it looks like BinStackingShardingFilterFactory.java pointing to the branched RuntimeCost annotation is causing the failures. I tried to change our test to point to the branched RuntimeCost annotation but Target '//third_party/bazel/src/java_tools/junitrunner/java/com/google/testing/junit/runner/sharding/weighted:weighted' is not visible. *** Original change description *** Branched internal RuntimeCost in junitrunner. RuntimeCost class is needed by the package com.google.testing.junit.runner.sharding.weighted. I branched it from the internal code because the weighted package is now open sourced and does not have access to the previous import. This didn't break Bazel before because there was no dependency to the weighted target when building BazelTestRunner. I catched this trying to open-source junitrunner tests. -- MOS_MIGRATED_REVID=135734237
{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.