The defaults can make use of variables passed by the project and I am
taking advantage of that feature in my templates.
With 70ed2236 / https://review.openstack.org/#/c/85336/ there is a
regression which cause the test to fail although it pass with parent
commit d833015.
Change-Id: I57d023657eec4f6f8f29980100185fcfd7e77b1f
This reverts commit 70ed22362a9c13ea9f3165e5747dcca281ad439c.
I knew I should have tested the patch with my own templates. Doing so I
discovered a nasty regression:
The defaults can make use of variables passed by the project. By moving
applyDEfaults to be called after deep_format is performed on job
templates, any substitutioncontained withing defaults is no longer
correctly replaced by project parameters.
Change-Id: I69ffb3e28093af6db62962786d9275bf3ba4e115
Make sure the example referenced in the documentation for ``Job Groups``
actually makes use of 'job-group'.
Change-Id: Ib78bdb459db23f57093c1fd4a6dd74a5080dc239
Add a few tests for JJB command processing. This is just to get
started I'm hoping more will come.
Change-Id: Iff964af025f6a3d7ba4acd91b1e0242285a11bc3
The zuul and zuul-post had sparse documentation, improve it a bit and
point to upstream documentation at:
http://ci.openstack.org/zuul/launchers.html#zuul-parameters
Add a note that Zuul 2.0 (gearman based) no longer requires those
parameters to be explicitly defined.
Change-Id: I1edcd5c3a101e2afe0025ad4cd3e511582998999
this option allows terminate job phase on specific status of job
Change-Id: I5984fb2494120afc97140c1ae38635301e8f1376
Signed-off-by: Lukas Bednar <lbednar@redhat.com>
Add support for local tags which are application specific to allow
including of other yaml files or code from scripts. Allows for code to
be maintained and tested as seperate files, as well as reduces
duplication of yaml code that cannot be macro'ed or easily templated by
including it from a common file.
Adds support for the following tags:
'include' - load file as yaml code
'include-raw' - load file as data (for scripts)
'include-raw-escaped' - load file as data with escaping braces '{}'
as default for use with job-templates
Use configuration file options to provide a search path for the files.
- Test behaviour of yaml tags independent of any XML generation
by comparing json result of yaml parsing to verify that certain
tags do/don't recall the yaml.load() method.
- Add examples for the include tags via addition tests for YamlParser
class
Inspired by
http://stackoverflow.com/questions/528281/how-can-i-include-an-yaml-file-inside-another
Change-Id: Ib90a07043112d4739d6529ceddbc9817668bcec0
Avoid the need to set the keep_descriptions option under the job_builder
section if providing any configuration options.
Change-Id: I0436a36e9f5ad7ff68ff5b92868ca1b13d019f11