Use 4c-16g builder for tox-verify jobs

The TransportPCE project does not appear to require 8 CPU system
to successfully build the Maven project. Looking at the Sonar and
CLM jobs this project builds just fine with the default
centos7-builder-4c-4g system.

TransportPCE does require 8g system for the tox-verify job though
due to it's use of Docker. There is no 4c-8g system available by
Vexxhost but there is a 4c-16g system which is about 33% cheaper
than the 8c-8g flavor.

Change-Id: Ib9c4b11749aec5d6eddef08bd8a708e858aaac50
Signed-off-by: Thanh Ha <zxiiro@gmail.com>

diff --git a/jjb/transportpce/transportpce.yaml b/jjb/transportpce/transportpce.yaml
index 762559292b35eca85f8a0c9c6201d3d9145ca8c1..a5ed92fb2d8be197941c1623d0deb3b8f13c7f11 100644 (file)
--- a/jjb/transportpce/transportpce.yaml
+++ b/jjb/transportpce/transportpce.yaml
@@ -9,7 +9,7 @@
           rtd-token: 6f37ba63226bdcc6c823ee455e62237cf68813fd
       - gerrit-tox-verify:
           build-timeout: 120
-          build-node: centos7-builder-8c-8g
+          build-node: centos7-builder-4c-16g
       - gerrit-release-merge
       - odl-maven-jobs-jdk11
       - odl-maven-verify-jobs
@@ -37,7 +37,7 @@
           rtd-token: 6f37ba63226bdcc6c823ee455e62237cf68813fd
       - gerrit-tox-verify:
           build-timeout: 120
-          build-node: centos7-builder-8c-8g
+          build-node: centos7-builder-4c-16g
       - odl-maven-jobs-jdk11
       - odl-maven-verify-jobs
 
@@ -64,7 +64,7 @@
           rtd-token: 6f37ba63226bdcc6c823ee455e62237cf68813fd
       - gerrit-tox-verify:
           build-timeout: 120
-          build-node: centos7-builder-8c-8g
+          build-node: centos7-builder-4c-16g
       - odl-maven-jobs
       - odl-maven-verify-jobs