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
The info on using list and dict as parameters seemed a little too advanced
to be in the description of 'templates'. This change moves this example into
a newly created 'advanced' configuration section.
Change-Id: I98b80233c45ac721819360743dcae5e82c63ecbf
Change I059f38d0aa8a8947aaac75e0ddb34d392063ece3 added support for
passing parameters to jobs in groups but not for variable substitution
on those parameters. Substitution on job list parameters would
be a new feature. This change removes a misleading parameter subsitution
example.
Partial-bug: #1298568
Change-Id: I18e28bb622f0473f049963ce6dcf6c4efd11dc2c
This axis requires the dynamic axis plugin:
https://wiki.jenkins-ci.org/display/JENKINS/DynamicAxis+Plugin
All the dynamic axis plugin settings are in the core project:
<matrix-project>
<axes>
<ca.silvermaplesolutions.jenkins.plugins.daxis.DynamicAxis>
<name>config</name>
<values>
<string>config_list</string>
</values>
<varName>config_list</varName>
<axisValues>
<string>default</string>
</axisValues>
</ca.silvermaplesolutions.jenkins.plugins.daxis.DynamicAxis>
</axes>
The plugin sets 2 values: axis name and variable name.
The axisValue element is hardcoded to 'default' in the plugin, so we do
the same in Jenkins job builder.
The matrix project supports multiple axes configuration, including dynamic
axis.
Tests added for:
* dynamic axis (by itself)
* multiple axes (dynamic and user-defined axes)
Tested on Jenkins LTS (1.554.2) with both the plugin installed and not
installed. The plugin is properly ignored in the latter case.
Change-Id: I36310bc512fd873fec4bd5f42937689fd178536e
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
The same job definition and examples were in both general.rst and
configuration.rst. Moved the contents of general to configuration.
Change-Id: Iefdf1b6ac3b9679a8af4451710442bf58054d790
Allow to SSH from master, instead of hardcoding to false.
It's particularly useful when the SSH credential are only
stored on the master. Default is kept to False.
Change-Id: I365cad043d30b6b290828a24635322c7f5afc35e
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
It was using a non-defined url variable and failed to me when running a
simple jenkins-jobs test -o ../outdir .
Change-Id: I56e6376de4972ea0f64bd8c81d6eb6d8f7f6d497
Signed-off-by: David Caro <dcaroest@redhat.com>
Remove samples and reference the tests as examples instead.
We don't need these samples for two reasons:
1. It is already duplicated in either JJB tests or documentation.
2. We don't test these samples so they may become outdated (some already have).
Change-Id: If1ba6cc8a675091e740fa254951bb8fcbcee6903
github.com/openstack-ci was moved to github.com/openstack-infra
homepage references should point to git.o.o/cgit/openstack-infra
This change updates the above references accordingly.
Change-Id: I4d3591f228b10de050a129ae7af99485f50edab5
pypi is not showing info from README.rst. This change adds a reference to the readme
so that it will appear on pypi.org upon a release of jjb.
Change-Id: I13b8d003d358bc1398058bbdbb5bb984ead2679b
Since version 2.11.0 the Gerrit Trigger Plugin can be configured to
generate patchset-created events for changes that were uploaded while
the connection to Gerrit was down.
Change-Id: I59608e4f01355944fed9e44b288fc25a897950c7