| commit | 0f10c42a8024c78a176c7a37048901ff28a725a7 | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Thu Jun 29 19:15:12 2017 +0600 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Mon Oct 02 08:53:45 2017 -0400 |
| tree | 8e5e5e297e17e3d344c2fed6144e1425dd9fbe07 | |
| parent | 888f49b22ec392d387f291fc33b5967af752f513 [diff] |
Add testing framework for Groovy pipelines - Create groovy_libraries for everything under jenkins/lib/src/... Should catch most groovy syntax errors. - Add a dummy test for bazelJob that at least verify that we can parse the library. This test is just printing the stack trace, ultimately it should be improved to parse the output of the pipeline and the mocks should be improved to be able to deal with various code path. Change-Id: I834b806c48640da923ae91269350330b584af7cd
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.
Finally, our docker rules needs authentication which is configured with the credential helper:
gcloud components install docker-credential-gcr export DOCKER_CONFIG="$(docker-credential-gcr configure-docker | sed -E 's|/config.json .*$||')"
You might want to permanently set your DOCKER_CONFIG environment, e.g. in your ~/.bash_profile:
echo "export DOCKER_CONFIG='${DOCKER_CONFIG}'" >> ~/.bash_profile
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.