jjb
/
jenkins-job-builder
Code Issues Proposed changes
Tools to make Jenkins jobs from templates
235 Commits 1 Branch 42 Tags 35 MiB
Python 99.1%
Shell 0.7%
Go to file
Will Soula fb582ad2dc Fixing defaults for email-ext 
If you go into Jenkins and just fill out the reipient list and click
save, Jenkins will default to having a Failure Trigger.  Jenkins
will also set the subject to $DEFAULT_SUBJECT and the content
to $DEFAULT_CONTENT.  This change is making JJB have the same
defaults for the email-ext functionality.  This way a user
can just set the recipient list and have it show up in Jenkins.
Previously just setting the reipient list lead to $DEFAULT_RECIPIENTS
being set instead with a FailureTrigger and this can be confusing
to some users.  This change also makes the recipient list default
to $DEFAULT_RECIPIENTS, like the plugin does when you first add
it to a job.  This way a user can just specify email-ext and the
global defaults will be used.

Change-Id: I8f207d495466a4a87431dbcb2cd46cb661b60ce1
Reviewed-on: https://review.openstack.org/19391
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Approved: James E. Blair <corvus@inaugust.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
 		2013-01-10 21:16:48 +00:00
doc Adding ability to specify the JDK to use. This change moves the top level config from builder.py into a separate file called general.py. This change also moves the assigned node work as well as the log rotator work into the general.py file. This change also adds the ability to specify the JDK for the build to use. 2012-12-19 03:18:32 +00:00
etc Add sample jenkins_jobs.ini configuration file 2012-10-30 19:22:36 +00:00
jenkins_jobs Fixing defaults for email-ext 2013-01-10 21:16:48 +00:00
samples Do not output XML if job name not specified ('pipeline', 'trigger-builds') 2012-10-30 16:32:39 +00:00
tools Adding ability to specify the JDK to use. This change moves the top level config from builder.py into a separate file called general.py. This change also moves the assigned node work as well as the log rotator work into the general.py file. This change also adds the ability to specify the JDK for the build to use. 2012-12-19 03:18:32 +00:00
.gitignore Update tox to exclude *egg for pep8 2012-11-20 17:03:18 +00:00
.gitreview Updated .gitreview location 2012-12-16 20:32:35 +00: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 Update README for project move. 2012-12-16 20:27:42 +00:00
openstack-common.conf Add openstack-common support for setup and version 2012-11-10 23:36:16 +00:00
setup.cfg Add openstack-common support for setup and version 2012-11-10 23:36:16 +00:00
setup.py Adding ability to use batch commands 2013-01-10 21:15:10 +00:00
tox.ini Bump pep8 to 1.3.3 2012-11-23 21:51:08 +00:00

README.rst

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:

Cloning:

Patches are submitted via Gerrit at:

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