commit: 6c31c76a3d9c04156af38d2f19ef40f1d105c2fb
[log]
author: Philipp Wollermann <philwo@google.com>
Thu Aug 10 12:41:58 2017 +0200
committer: Philipp Wollermann <philwo@google.com>
Thu Aug 10 12:41:58 2017 +0200
tree: 7d36539befdbb72e9528e31d16a62b0f5a1bcfaa
parent: 2b8b11e01113398fd404a5676859cabb47d7b763 [diff]

Do not try to install the jdk7 flavor of Bazel in gce/bootstrap-bazel.sh

It no longer exists.

Change-Id: I69f0f055e0d3bb4feb30328c1ddc30738b4cb9f0

gce/bootstrap-bazel.sh[diff]

1 file changed

tree: 7d36539befdbb72e9528e31d16a62b0f5a1bcfaa

README.md

Bazel continous integration setup

This workspace contains the setup for the continuous integration system of Bazel. This setup is based on docker images built by bazel.

For users of Bazel continuous integration system

If you are a user of the CI system, you might be interested in the following document:

owner: explains how to add a job for a repository owner.
user: explains how to use the CI system for a Bazel contributor.

For maintainers of Bazel continuous integration system

Make sure you have a Bazel installed with a recent enough version of it. Also make sure gcloud and docker are correctly configured on your machine. Only docker version 1.10 or later is supported.

More documentation:

init.sh: initializes the whole CI platform. This may delete VMs and do other irreversible changes, so handle with care.
vm.sh: lets you control the machines (e.g. start/stop them, create/delete/reimage them), including the Jenkins controller and the executor nodes.
workflow: explains the CI workflow, and how you can test local changes with jenkins-staging
jobs: explains what jobs are running on the CI