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.
Thanh Ha c33dbaaaae
Revert "Allow dashes in variable key names"
9 months ago
doc adopt pre-commit hooks 10 months ago
etc Add convenience function for plugin namespace 2 years ago
jenkins_jobs Revert "Allow dashes in variable key names" 9 months ago
samples reference tests as examples 5 years ago
tests Merge "Add support for "Invoke Nexus Policy Evaluation"" 10 months ago
tools Allow jjb to be called as a module 11 months ago
.gitignore Replace testr with stestr 1 year ago
.gitreview Updated .gitreview location 6 years ago
.pre-commit-config.yaml adopt pre-commit hooks 10 months ago
.stestr.conf Replace testr with stestr 1 year ago
.zuul.yaml Enable cross testing with python-jenkins 1 year ago
LICENSE Add a LICENSE file. 6 years ago Just give in and use setuptools_git. 6 years ago
README.rst adopt pre-commit hooks 10 months ago
docs-requirements.txt Add a requirements file for readthedocs 3 years ago
requirements.txt Constrain PyYAML to v3.x. 11 months ago
setup.cfg adopt pre-commit hooks 10 months ago Sync requirements with openstack/requirements 2 years ago
test-requirements.txt adopt pre-commit hooks 10 months ago
tox.ini adopt pre-commit hooks 10 months ago



Jenkins Job Builder takes simple descriptions of Jenkins jobs in YAML or JSON 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:

$ pip install --user jenkins-job-builder

Online documentation:


Bug report:



git clone

Install pre-commit from in order to run some minimal testing on your commits.

A virtual environment is recommended for development. For example, Jenkins Job Builder may be installed from the top level directory:

$ virtualenv .venv
$ source .venv/bin/activate
$ pip install -r test-requirements.txt -e .

Patches are submitted via Gerrit at:

Please do not submit GitHub pull requests, they will be automatically closed.

Mailing list:


  • #openstack-jjb on Freenode

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.

Unit Tests

Unit tests have been included and are in the tests folder. Many unit tests samples are included as examples in our documentation to ensure that examples are kept current with existing behaviour. To run the unit tests, execute the command:

tox -e py34,py27
  • Note: View tox.ini to run tests on other versions of Python, generating the documentation and additionally for any special notes on running the test to validate documentation external URLs from behind proxies.

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