eebb71cbb3
The archive publisher did not allow setting the allowEmptyArchive setting in the YAML. This change adds configuring the setting if it is defined in the YAML file. If the value is 'true' then it is set, else it is 'false'. The default Jenkins behavior is 'false' disallowing builds to pass without storing the archived data. Updated the doc string to add that there is a default value (false) which is also the default Jenkins behavior. Cleand up the value assignment, and typed it to a str(). fixed pep8 violation Addresses patchset 3 request to update the doc string to use the test directly. Would like to have more discussion around the second point in patchset 3 around having the new code add a line of XML. Change-Id: I5e0c9ed7e8ea669a8d0e8f267ebb02d5f0b6ae73 |
||
---|---|---|
doc | ||
etc | ||
jenkins_jobs | ||
samples | ||
tests | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
README.rst | ||
setup.cfg | ||
setup.py | ||
tox.ini |
Jenkins Job Builder
Jenkins Job Builder takes simple descriptions of Jenkins jobs in YAML format, and uses them to configure Jenkins. You can keep your job descriptions in human readable text format in a version control system to make changes and auditing easier. It also has a flexible template system, so creating many similarly configured jobs is easy.
To install:
$ sudo python setup.py install
Online documentation:
Developers
Bug report:
Cloning:
Patches are submitted via Gerrit at:
More details on how you can contribute is available on our wiki at:
Writing a patch
We ask that all code submissions be pep8 and pyflakes clean. The easiest way to do that is to run tox before submitting code for review in Gerrit. It will run pep8 and pyflakes in the same manner as the automated test suite that will run on proposed patchsets.
When creating new YAML components, please observe the following style conventions:
- All YAML identifiers (including component names and arguments) should be lower-case and multiple word identifiers should use hyphens. E.g., "build-trigger".
- The Python functions that implement components should have the same name as the YAML keyword, but should use underscores instead of hyphens. E.g., "build_trigger".
This consistency will help users avoid simple mistakes when writing YAML, as well as developers when matching YAML components to Python implementation.
Installing without setup.py
For YAML support, you will need libyaml installed.
Mac OS X:
$ brew install libyaml
Then install the required python packages using pip:
$ sudo pip install PyYAML python-jenkins