jjb
/
jenkins-job-builder
Code Issues Proposed changes
Tools to make Jenkins jobs from templates
1,316 Commits 1 Branch 42 Tags 35 MiB
Python 99.1%
Shell 0.7%
Go to file
Jenkins f1c34249cc Merge "Adding publisher support to join-trigger plugin" 2015-07-27 02:05:14 +00:00
doc Fix two typos and Fix readability 2015-07-27 09:10:57 +09:00
etc Only query jenkins plugins if config provided 2015-04-17 17:16:33 +01:00
jenkins_jobs Merge "Adding publisher support to join-trigger plugin" 2015-07-27 02:05:14 +00:00
samples reference tests as examples 2014-05-29 09:30:49 -07:00
tests Merge "Adding publisher support to join-trigger plugin" 2015-07-27 02:05:14 +00:00
tools Change zuul-cloner parameters 2015-06-15 11:08:08 -07:00
.gitignore Ignore testr_subunit_log 2014-10-21 11:02:40 +08:00
.gitreview Updated .gitreview location 2012-12-16 20:32:35 +00:00
.testr.conf Tests for publishers 2013-07-19 14:31:11 +02:00
LICENSE Add a LICENSE file. 2012-11-16 00:22:31 +00:00
MANIFEST.in Just give in and use setuptools_git. 2012-11-20 14:15:58 +00:00
README.rst Replace ci.o.o links with docs.o.o/infra 2015-05-28 06:28:47 +00:00
requirements.txt requirements: pin pbr>=0.8.2,<2.0 2015-06-09 17:40:26 -04:00
setup.cfg Merge "Adding Flowdock as a supported publisher" 2015-07-21 01:13:54 +00:00
setup.py Migrate to pbr 2014-03-14 22:25:46 +01:00
test-requirements.txt Support hacking module <= 0.10.1 2015-03-03 01:10:26 +00:00
tox.ini Exclude .test directory from pep8 check 2015-07-07 16:43:24 +01:00

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