The problem with nesting variables in defaults.yaml is it causes
everyone, regardless of if they care about streamtestplan to
require the variables defined in streamtestplan to be required in
their templates. This is causes job-templates that never needed
these variables to have to define a dummy variable in order to
successfully pass.
Considering no existing csit jobs override the 'streamtestplan'
variable, remove it as a option and code the pattern into the
job-templates that use it.
Change-Id: Ib2355753031a908aafa7e43bcc01c34cce770e93
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
scriptplan: '{project}.txt'
configplan: '{project}.txt'
testplan: '{project}-{functionality}.txt'
- streamtestplan: '{project}-{functionality}-{stream}.txt'
karaf-version: karaf4
build-days-to-keep: 30
use-features-boot: 'True'
- integration-config-plan:
config-plan: '{configplan}'
- integration-stream-test-plan:
- stream-test-plan: '{streamtestplan}'
+ stream-test-plan: '{project}-{functionality}-{stream}.txt'
- integration-test-plan:
test-plan: '{testplan}'
- integration-test-suites:
- integration-config-plan:
config-plan: '{configplan}'
- integration-stream-test-plan:
- stream-test-plan: '{streamtestplan}'
+ stream-test-plan: '{project}-{functionality}-{stream}.txt'
- integration-test-plan:
test-plan: '{testplan}'
- integration-test-suites: