After monitoring the system a bit and looking at the jobs. The none
distribution-test jobs do not queue very many csit jobs and if we
tie them to the distro-test queue these jobs would not benefit much
from parallel csit runs. Let's give them their own separate queue
instead with a larger pool of allowed job runs.
Use NUM_EXECUTORS so that we can use the same VM to launch multiple
jobs considering that these jobs do not do anything other than launch
other csit jobs.
Change-Id: Ide261d2550ff69da4fd0f30857f7358f2c7f9cb6
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
--- /dev/null
+IMAGE_NAME=ZZCI - CentOS 7 - robot - 20180109-1917
+HARDWARE_ID=v1-standard-1
+INSTANCE_CAP=1
+NUM_EXECUTORS=4
name: 'integration-sanity-test-{stream}'
project-type: freestyle
name: 'integration-sanity-test-{stream}'
project-type: freestyle
- node: queue-disttest-2c-1g
+ node: queue-intque-2c-1g
properties:
- opendaylight-infra-properties:
properties:
- opendaylight-infra-properties:
name: 'integration-distribution-weekly-test-trigger-{stream}'
project-type: freestyle
name: 'integration-distribution-weekly-test-trigger-{stream}'
project-type: freestyle
- node: queue-disttest-2c-1g
+ node: queue-intque-2c-1g
properties:
- opendaylight-infra-properties:
properties:
- opendaylight-infra-properties:
name: 'integration-distribution-high-frequency-test-trigger-{stream}'
project-type: freestyle
name: 'integration-distribution-high-frequency-test-trigger-{stream}'
project-type: freestyle
- node: queue-disttest-2c-1g
+ node: queue-intque-2c-1g
properties:
- opendaylight-infra-properties:
properties:
- opendaylight-infra-properties: