| commit | bb7ca643c881dcfd57f91f36df21a8c3bd835bf0 | [log] [tgz] |
|---|---|---|
| author | Kailash Khalasi <kailash@onlab.us> | Wed Apr 11 13:35:17 2018 -0700 |
| committer | Kailash Khalasi <kailash@onlab.us> | Wed Apr 11 13:42:09 2018 -0700 |
| tree | 9c8460d8ac427f4ce83d7610f8394778692c31d0 | |
| parent | e64341b9a6acfe2f881e20eb99637fd5ab1599b1 [diff] |
adding devnode parameter to nightly build job Change-Id: Ica3dedbf19e774b96386258e7f6fe00326fa75ea
This repo holds configuration for the Jenkins testing infrastructure used by CORD.
The best way to work with this repo is to check it out with repo, per these instructions: Downloading testing and QA repositories
NOTE: This repo uses git submodules. If you have trouble with the tests or other tasks, please run:
git submodule init && git submodule updateto obtain these submodules, asrepowon't do this automatically for you.
JJB job definitions can be tested by running:
make test
Which will create a python virtualenv, install jenkins-job-builder in it, then try building all the job files, which are put in job-configs and can be inspected.
There are a few useful macros defined in jjb/cord-macros.yml
cord-infra-properties - sets build discarder settingscord-infra-gerrit-repo-scm - checks out the entire source tree with the repo toolcord-infra-gerrit-repo-patch - checks out a patch to a git repo within a checked out repo source tree (WIP, doesn't work yet)cord-infra-gerrit-trigger-patchset - triggers build on gerrit new patchset, draft publishing, comments, etc.cord-infra-gerrit-trigger-merge - triggers build on gerrit mergeIf you make changes which create a new packer image, you have to manually set the instance AMI ID on jenkins in Global Config > Cloud > Amazon EC2.
If you create a new cloud instance type, make sure to set both the Security group names and Subnet ID for VPC or it will fail to instantiate.