| commit | 23c725b6824e7beac753779a5abeeb44c9be3bda | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Fri Oct 02 16:31:55 2015 +0000 |
| committer | Dmitry Lomov <dslomov@google.com> | Fri Oct 02 18:02:42 2015 +0000 |
| tree | a2e6c696529731559b07ded8009fa73e425b58b4 | |
| parent | 5f5991dfea02e1741de598ab207c2ece9659991d [diff] |
Fix Java 7 test suite
- Prevent test from JavaBuilder to be run (mark them as JDK8 only).
- Hack to replace the JavaBuilder target so that test that needs JavaBuilder
will depends on the pre-built binary version.
Tested: bash -c 'export JAVA_VERSION=1.7; source scripts/ci/build.sh; bazel_build'
(and verified that there is no build failure). We might still have failing
tests (worker and runfiles) but the failure seems like flakiness.
--
MOS_MIGRATED_REVID=104504123
{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.