Change-Id: I1a12cebe248c368bab73abd50cc5045214435b8f
Signed-off-by: Anil Belur <abelur@linuxfoundation.org>
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
"{project-name}-ci-jobs" job-group and does not need to be explicitly called if
the job group is being used.
-Miniaml Example:
+Minimal Example:
.. literalinclude:: ../../.jjb-test/lf-ci-jobs/jenkins-cfg-merge-minimal.yaml
:language: yaml
(default: "os-cloud")
:INSTANCE_CAP: Total number of instances the cloud will allow spin up.
(default: null)
- :SANDBOX_CAP: Total number of instances the clodu will allow to
+ :SANDBOX_CAP: Total number of instances the cloud will allow to
spin up. This applies to "sandbox" systems and overrides the
INSTANCE_CAP setting. (default: null)