98b69476ea
I had the use case of a lot of projects sharing the same job template that uses a lot of variables. That requires each project to define all the variables even if they are mostly identical. This patch propose to define varialbes as 'defaults' and have them applied in the job-template magically (oneline diffs always have that feeling to me). So instead of: - project: name: project1 arch: amd64 builder: debuild lintian: true jobs: - '{name}-build-{arch}' And so on ... I can just: - defaults: name: sanebuild - project: name: project1 defaults: sanebuild jobs: - '{name}-build-{arch}' And override the arch as needed either in the project or by passing it to the job. Without this patch, the provided yamlparser fixture template_honor_defaults.yaml would raise: arch parameter missing to format echo Build arch {arch}. Given: {'': '', 'jobs': ['build-{arch}'], 'name': 'project-name'} Change-Id: Ida1e27eb47356d9cae42175743bd2fd52eb9d869 |
||
---|---|---|
doc | ||
etc | ||
jenkins_jobs | ||
samples | ||
tests | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
openstack-common.conf | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
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:
Please do not submit GitHub pull requests, they will be automatically closed.
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