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.
 
 
Monty Taylor 7f7cac2cd5 Just give in and use setuptools_git. 10 years ago
doc Add option to block up|down stream builds. 10 years ago
etc Add sample jenkins_jobs.ini configuration file 10 years ago
jenkins_jobs Add copyartifact builder to entry points and fix target attribute 10 years ago
samples Do not output XML if job name not specified ('pipeline', 'trigger-builds') 10 years ago
tools Do not output XML if job name not specified ('pipeline', 'trigger-builds') 10 years ago
.gitignore Add openstack-common support for setup and version 10 years ago
.gitreview Add .gitreview. 10 years ago
LICENSE Add a LICENSE file. 10 years ago
MANIFEST.in Just give in and use setuptools_git. 10 years ago
README.md Add some style developer docs. 10 years ago
openstack-common.conf Add openstack-common support for setup and version 10 years ago
setup.cfg Add openstack-common support for setup and version 10 years ago
setup.py Just give in and use setuptools_git. 10 years ago
tox.ini Use console_scripts entrypoint. 10 years ago

README.md

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: https://bugs.launchpad.net/openstack-ci/

Cloning: https://github.com/openstack-ci/jenkins-job-builder.git

Patches are submitted via Gerrit at https://review.openstack.org/

More details on how you can contribute is available on our wiki at: http://wiki.openstack.org/HowToContribute

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