- shell: !include-raw:
- ../shell/logs-get-credentials.sh
- shell: !include-raw:
- - ../shell/lftools-install.sh
- ../shell/logs-deploy.sh
- shell: !include-raw:
- ../shell/logs-clear-credentials.sh
3 basic steps:
1. Provide credentials via config-file-provider
-2. Run the build scripts in this case lftools-install.sh and logs-deploy.sh
+2. Run logs-deploy.sh
3. Remove credentials provided by config-file-provider
.. _preserve-variable-refs:
JJB has an option to preserve a data structure object when you want to pass
it to a template.
-https://docs.openstack.org/infra/jenkins-job-builder/definition.html#variable-references
+https://jenkins-job-builder.readthedocs.io/en/latest/definition.html#variable-references
One thing that is not explicitly covered is the format of the variable name
that you pass the object to. When you use the `{obj:key}` notation to preserve
.. literalinclude:: _static/github-pr-trigger.example
-In the above example note the use of underscores in ``github_pr_whitelist``,
+In the above example note the use of underscores in ``github_pr_allowlist``,
``github_pr_admin_list``, and ``github_included_regions``.
Using single quotes around variables
If we do not declare a default in the :ref:`job-template <job-template>` then
JJB will fallback to checking the "defaults configuration".
-This means that the precendence of defaults is as follows:
+This means that the precedence of defaults is as follows:
1. User-provided
2. Job Template
global-jjb should not provide job-group definitions and leave it up to users of
global-jjb to create their own as a job-group as a variable defined in a job
-group the highest precendence. Global JJB should strive to be purely a
+group the highest precedence. Global JJB should strive to be purely a
job-template and macro library for downstream consumers.
Final thoughts