Bazel: Introduce .bazelversion and update to 0.29.1

The minimum required bazel version is defined in the WORKSPACE and is
checked at build time. However, to support the bazelisk wrapper, we
need to define the version in .bazelversion. Bazelisk will automatically
switch to that version (downloading it if necessary).

Add a .bazelversion file, and introduce the mechanism to consume it in
the WORKSPACE rather than defining the version in two separate places.

When bazel is used directly, it still checks that the minimum version
is used. When bazelisk is used, it will switch to the exact required

Bump the bazel version up to 0.29.1 as the currently specified minimum
version (0.19.0) doesn't work with this new setup.

Based on [1] by David Ostrovsky.


Change-Id: I6fe6d2e1f16b15bbad80979fcb8d76f843f69a19
3 files changed
tree: 6d5e45ccb000dcca10756820a19f00d9e09c71f2
  1. .settings/
  2. Documentation/
  3. java/
  4. javatests/
  5. lib/
  6. resources/
  7. tools/
  8. .bazelrc
  9. .bazelversion
  10. .gitignore
  11. .mailmap
  12. BUILD
  14. fake_pom_deploy.xml
  17. version.bzl

Gitiles - A simple JGit repository browser

Gitiles is a simple repository browser for Git repositories, built on JGit. Its guiding principle is simplicity: it has no formal access controls, no write access, no fancy Javascript, etc.

Gitiles automatically renders *.md Markdown files into HTML for simplified documentation. Refer to the Markdown documentation for details.


Gitiles is configurable in a git-style configuration file named gitiles.config. Refer to the configuration documentation for details.


Use the issue tracker at github to file bugs.

Contributing to Gitiles

Please refer to the Developer Guide.