Google Git
Sign in
bazel / bazel / 075b39d85a5e5aaf82a83dc07d2ea7ca7385a47f
commit075b39d85a5e5aaf82a83dc07d2ea7ca7385a47f[log] [tgz]
authorDamien Martin-Guillerez <dmarting@google.com>Mon Jun 15 15:55:34 2015 +0000
committerKristina Chodorow <kchodorow@google.com>Tue Jun 16 13:58:46 2015 +0000
tree7a47e7b72fe1596d6c7bffe84e9e426345b29ffb
parent65f422376467aa2369e2e1a7bb0ba8fc2e69393b [diff]
Set-up travis OSX to compile using JDK 7

This is introducing a few changes to use the Java compiler
from errorprone:
  - add the --java_langtools flag to the shell tests so
    we do the tests with the same java compiler tooling than
    Bazel, and
  - added the langtools the bootclasspath of the JavaBuilder
    tests.
  - tagged some tests and deactivated them on travis OSX
    because they either requires Java 8 or a lot of disk
    space.

To do the same change on a local install, one must:
  - change the source and target versions to 7 in the
    tools/jdk:toolchain target,
  - use the .travis/jdk7.WORKSPACE file instead of the
    default Bazel workspace (it contains a maven_jar
    refering to the errorprone's java compiler tools), and
  - set the JAVA_VERSION environent variable to "1.7".
The .travis/build.sh script does just that when under OS X.

--
Change-Id: Idb466cf47cf7df35a34fb0dd8d186628aae0cba7
Reviewed-on: https://bazel-review.googlesource.com/#/c/1520/
MOS_MIGRATED_REVID=96011123
7 files changed
tree: 7a47e7b72fe1596d6c7bffe84e9e426345b29ffb
  1. .travis/
  2. examples/
  3. scripts/
  4. site/
  5. src/
  6. third_party/
  7. tools/
  8. .gitattributes
  9. .gitignore
  10. .travis.yml
  11. compile.sh
  12. CONTRIBUTING.md
  13. LICENSE.txt
  14. README.md
  15. WORKSPACE
README.md

Bazel (Alpha)

{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.

Getting Started

Build Status