re-arrange docs for clarity
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
This commit is contained in:
parent
3696fdaba2
commit
b38c5e46ac
|
@ -123,12 +123,6 @@ define a template that you can use to create jobs with a `Project`_
|
|||
definition. It's name will depend on what is supplied to the
|
||||
`Project`_.
|
||||
|
||||
If you want to use lists or dicts variables you can use ``{obj:key}``.
|
||||
|
||||
For example:
|
||||
|
||||
.. literalinclude:: /../../tests/yamlparser/fixtures/custom_distri.yaml
|
||||
|
||||
.. _project:
|
||||
|
||||
Project
|
||||
|
@ -309,6 +303,17 @@ definitions unless they specify a different Default object with the
|
|||
|
||||
Will set the job description for every job created.
|
||||
|
||||
.. _advanced:
|
||||
|
||||
Advanced
|
||||
^^^^^^^^
|
||||
|
||||
If you want to use lists or dicts variables you can use ``{obj:key}``.
|
||||
|
||||
For example:
|
||||
|
||||
.. literalinclude:: /../../tests/yamlparser/fixtures/custom_distri.yaml
|
||||
|
||||
|
||||
Modules
|
||||
-------
|
||||
|
|
Loading…
Reference in New Issue