Manuel Desbonnet 211cd36318 Do not output XML if job name not specified ('pipeline', 'trigger-builds')

Done in order to enable specifying build pipelines at the project level.
Pipelines are built using the 'pipeline' plugin or the 'trigger-builds'
plugin.  The downstream job to be executed is specified at the project
level, and substituted into the template.  Ignoring definitions where
the downstream job is blank allows the pipeline to be easily terminated.

Also adding a samples/ directory, which currently contains an example of
pipeline creation, together with a new tools/run-compare-xml-samples.sh
to run the before/after test on the samples.

Change-Id: Icc324d1485e22db7824ad784890db48eb3e48f8f
Reviewed-on: https://review.openstack.org/13706
Reviewed-by: James E. Blair <corvus@inaugust.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Approved: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins

2012-10-30 16:32:39 +00:00

317 B

Raw Blame History

Jenkins Job Builder Examples

These examples demonstrate the use of particular features of Jenkins Job Builder that can be used as starting points for new projects.

These examples are also used in the test framework - if you add a new example here, please ensure that it can be processed by Jenkins Job Builder.

317 B Raw Blame History

Jenkins Job Builder Examples

317 B

Raw Blame History