Update the build node used for multicloud-k8s

The multicloud-k8s build uses golang plugins and
these builds are parallelized. The linker uses
about 920MB per plugin during the link phase and this
is causing the build machine to run out of memory where
we are compiling 4+ plugins on the system.

Issue-ID: MULTICLOUD-666
Change-Id: I796fdf5883729d6d805d56a9754fb3b032e13995
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>

diff --git a/jjb/multicloud/multicloud-k8s.yaml b/jjb/multicloud/multicloud-k8s.yaml
index c015a67..4d368af 100644 (file)
--- a/jjb/multicloud/multicloud-k8s.yaml
+++ b/jjb/multicloud/multicloud-k8s.yaml
@@ -22,7 +22,7 @@
     mvn-settings: 'multicloud-k8s-settings'
     files: '**'
     archive-artifacts: ''
-    build-node: ubuntu1604-builder-4c-4g
+    build-node: ubuntu1604-builder-8c-8g
 
 #- project:
 #    name: multicloud-k8s-arm64