Tools to make Jenkins jobs from templates
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Khai Do f594fb5c7c reference tests as examples 9 years ago
doc Test creation of multiple jobs from templates 9 years ago
etc Added config options to not overwrite jobs desc 9 years ago
jenkins_jobs Merge "Fail if specified set of defaults is not found." 9 years ago
samples reference tests as examples 9 years ago
tests scms: MultiSCM is generated for scms hidden in macro 9 years ago
tools Migrate to pbr 9 years ago
.gitignore Doc: Use VersionInfo from pbr and remove openstack common modules 9 years ago
.gitreview Updated .gitreview location 10 years ago
.testr.conf Tests for publishers 10 years ago
LICENSE Add a LICENSE file. 10 years ago Just give in and use setuptools_git. 10 years ago
README.rst Merge "README.rst: Add links" 9 years ago
openstack-common.conf Add openstack-common support for setup and version 10 years ago
requirements.txt Migrate to pbr 9 years ago
setup.cfg add overview info to pypi 9 years ago Migrate to pbr 9 years ago
test-requirements.txt Add hacking to requirements 9 years ago
tox.ini Add hacking to requirements 9 years ago


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 install

Online documentation:


Bug report:


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

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