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 cc68019f07 Add a requirements file for readthedocs 7 years ago
doc Fix two typos and Fix readability 7 years ago
etc Only query jenkins plugins if config provided 8 years ago
jenkins_jobs Merge "Adding publisher support to join-trigger plugin" 7 years ago
samples reference tests as examples 9 years ago
tests Merge "Adding publisher support to join-trigger plugin" 7 years ago
tools Change zuul-cloner parameters 8 years ago
.gitignore Ignore testr_subunit_log 8 years ago
.gitreview Updated .gitreview location 10 years ago
.testr.conf Tests for publishers 9 years ago
LICENSE Add a LICENSE file. 10 years ago
MANIFEST.in Just give in and use setuptools_git. 10 years ago
README.rst Replace ci.o.o links with docs.o.o/infra 8 years ago
docs-requirements.txt Add a requirements file for readthedocs 7 years ago
requirements.txt requirements: pin pbr>=0.8.2,<2.0 8 years ago
setup.cfg Merge "Adding Flowdock as a supported publisher" 7 years ago
setup.py Migrate to pbr 9 years ago
test-requirements.txt Support hacking module <= 0.10.1 8 years ago
tox.ini Exclude .test directory from pep8 check 7 years ago

README.rst

README

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:

Repository:

Cloning:

git clone https://git.openstack.org/openstack-infra/jenkins-job-builder

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