Ideally we should verify this at build time, but until then, at least
make the examples syntactically valid for anybody trying to get
started.
Change-Id: I413ae9576b012a4847bedaa5a1582fad3e1a8de0
Reviewed-on: https://review.openstack.org/15018
Approved: James E. Blair <corvus@inaugust.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
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
This change allows constructs like:
- job-template:
name: "foo-build-{slave}"
- project:
slave:
- debian-squeeze-powerpc
- debian-squeeze-amd64
and will then instantiate the job template for each value in the
list.
Change-Id: I057a30ef6d91048efacc4a6da2142cb8f924dd06
Reviewed-on: https://review.openstack.org/14738
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
The motivation for this was to allow for specifying a pipeline of jobs
at the project level, thereby re-using the same job templates in
different pipelines.
Change-Id: I9840d3713669ceca75a831be92c95c3fe9195c01
Reviewed-on: https://review.openstack.org/13705
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
Sphinx was unable to find the jenkins_jobs.sphinx.yaml module when I
ran 'make html' in the doc/ subdirectory.
Change-Id: I64817139b149c66b01e3610248b49f955c5bde8c
Reviewed-on: https://review.openstack.org/13707
Reviewed-by: James E. Blair <corvus@inaugust.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Approved: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
Tweaks the Builder and YamlParser classes to accept a config object
which is passed to the parser's ModuleRegistry object. This makes it
available to the HipChat object.
Change-Id: I3017658336b949c0fda7c82945e7014dbcf6e152
Reviewed-on: https://review.openstack.org/12794
Reviewed-by: James E. Blair <corvus@inaugust.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Approved: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
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