Update documentation on Macros
Change-Id: I177a3eea4b4f9732934bb861c02c5f7781ee6d7e
This commit is contained in:
parent
f6e2b405c4
commit
97bc4e69cf
@ -377,31 +377,6 @@ Then ``<builders />`` section of the generated job show up as::
|
||||
As you can see, the specialized macro ``addtwo`` reused the definition from
|
||||
the generic macro ``add``.
|
||||
|
||||
Macro Notes
|
||||
~~~~~~~~~~~
|
||||
|
||||
Macros are expanded using Python string substitution rules. This can
|
||||
especially cause confusion with shell snippets that use ``{`` and ``}`` as part
|
||||
of their syntax. You must escape curly braces you wish to make it through
|
||||
to the output, e.g.::
|
||||
|
||||
- builder:
|
||||
name: a_builder
|
||||
builders:
|
||||
- shell: |
|
||||
PARAMETER={parameter}
|
||||
VARIABLE=${{VARIABLE:-bar}}
|
||||
function foo {{
|
||||
echo "my shell function"
|
||||
}}
|
||||
|
||||
The same apply for ``job`` and ``job-template``. Thus embedded-shell within
|
||||
a ``job`` or ``job-template`` should always use ``{{`` to achieve a literal
|
||||
``{``.
|
||||
|
||||
You can also use ``!j2:`` tag instead - Jinja2 uses double quotes for variables.
|
||||
|
||||
|
||||
.. _folders:
|
||||
|
||||
Folders
|
||||
|
Loading…
x
Reference in New Issue
Block a user