Fuel has 2 non-CI PODs: zte-pod1 and itri-pod1.
Since these PODs do not use slave labels but explicit node name
targeting, we need to define testing project jobs for them.
Change-Id: Ibb6e9c072c64fe2c41b60bd65d079c32f6b0c074
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
slave-label: armband-baremetal
installer: fuel
<<: *hunter
slave-label: armband-baremetal
installer: fuel
<<: *hunter
+ # fuel NONE CI PODs
+ - zte-pod1:
+ slave-label: fuel-baremetal
+ installer: fuel
+ <<: *master
+ - itri-pod1:
+ slave-label: fuel-baremetal
+ installer: fuel
+ <<: *master
installer: joid
auto-trigger-name: 'daily-trigger-disabled'
<<: *master
installer: joid
auto-trigger-name: 'daily-trigger-disabled'
<<: *master
+ - itri-pod1:
+ slave-label: '{pod}'
+ installer: fuel
+ auto-trigger-name: 'daily-trigger-disabled'
+ <<: *master
- zte-pod1:
slave-label: '{pod}'
installer: fuel
- zte-pod1:
slave-label: '{pod}'
installer: fuel
default: '-i 104.197.68.199:8086'
description: 'Arguments to use in order to choose the backend DB'
default: '-i 104.197.68.199:8086'
description: 'Arguments to use in order to choose the backend DB'
+- parameter:
+ name: 'yardstick-params-itri-pod1'
+ parameters:
+ - string:
+ name: YARDSTICK_DB_BACKEND
+ default: '-i 104.197.68.199:8086'
+ description: 'Arguments to use in order to choose the backend DB'
+
- parameter:
name: 'yardstick-params-zte-pod1'
parameters:
- parameter:
name: 'yardstick-params-zte-pod1'
parameters: