ab7c6bc6c1
Move test.sh to the tools directory. Move parameters and notifications to their own modules; even though they are implemented as Jenkins properties, they make more sense as separate entities in the job builder, because that's they way they are specified in the YAML. All three modules that touch the properties xml object know how to create it if it's missing. Change-Id: I4b42ff10a93fd3ed98f632b58e47f3e0e45086d6 Reviewed-on: https://review.openstack.org/12741 Reviewed-by: Clark Boylan <clark.boylan@gmail.com> Approved: James E. Blair <corvus@inaugust.com> Tested-by: Jenkins
35 lines
861 B
ReStructuredText
35 lines
861 B
ReStructuredText
.. Jenkins Job Builder documentation master file, created by
|
|
sphinx-quickstart on Mon Sep 10 19:36:21 2012.
|
|
You can adapt this file completely to your liking, but it should at least
|
|
contain the root `toctree` directive.
|
|
|
|
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.
|
|
|
|
|
|
.. _Jenkins: http://jenkins-ci.org/
|
|
.. _YAML: http://www.yaml.org/
|
|
|
|
Contents:
|
|
|
|
.. toctree::
|
|
:maxdepth: 3
|
|
|
|
installation
|
|
configuration
|
|
extending
|
|
|
|
Indices and tables
|
|
==================
|
|
|
|
* :ref:`genindex`
|
|
* :ref:`modindex`
|
|
* :ref:`search`
|
|
|