Modifying the ci-mgmt flavor to use v2 while we figure out what the
issue is with the v3 flavors.
Noticed the merge job is using the wrong builder so I switched it to the
4c-4g builder.
Signed-off-by: Vanessa Rene Valderrama <vvalderrama@linuxfoundation.org>
Change-Id: I23c5e9ab21711d8545fdbcd12baeb1cfc55a3662
IMAGE_NAME=ZZCI - CentOS 7 - builder - x86_64 - 20200115-151843.366
LABELS=centos7-builder-2c-2g
-HARDWARE_ID=v3-standard-2
+HARDWARE_ID=v2-highcpu-2
VOLUME_SIZE=40
IMAGE_NAME=ZZCI - CentOS 7 - builder - x86_64 - 20200115-151843.366
LABELS=centos7-builder-4c-4g
-HARDWARE_ID=v3-standard-4
+HARDWARE_ID=v2-highcpu-2
VOLUME_SIZE=40
# Default Template Configuration
IMAGE_NAME=ZZCI - CentOS 7 - builder - x86_64 - 20200115-151843.366
VOLUME_SIZE=20
-HARDWARE_ID=v3-standard-2
+HARDWARE_ID=v2-highcpu-2
NETWORK_ID=bcb9a62c-5a82-4293-a8c6-d73e8c2dbd03
USER_DATA_ID=jenkins-init-system
INSTANCE_CAP=20
- gerrit-jenkins-sandbox-cleanup
- gerrit-jjb-deploy-job
- gerrit-jjb-merge:
- build-node: centos7-builder-8c-8g
+ build-node: centos7-builder-4c-4g
- gerrit-jjb-verify
project: ci-management