commit | c9d561ecd5ffa0e0ed824408a21db81259a2bc59 | [log] [tgz] |
---|---|---|
author | Klaus Aehlig <aehlig@google.com> | Tue Jul 25 14:53:35 2017 +0200 |
committer | Klaus Aehlig <aehlig@google.com> | Tue Jul 25 16:42:58 2017 +0200 |
tree | 8551354703883f4a5c4683095f903fefeef847a1 | |
parent | 8f36d5a829d69c489dc3e118e7047d78bf618fe4 [diff] |
Run basic integration tests of FreeBSD Test at least //src/test/shell/integration/... on FreeBSD. Note that the code cannot be used as is; instead we have to replay the USES=shebangfix of the port. First step for #54. Change-Id: I1ec52a0163000f034ef479ba0502697752b198ed
This workspace contains the setup for the continuous integration system of Bazel. This setup is based on docker images built by bazel.
If you are a user of the CI system, you might be interested in the following document:
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.