Tunning vms parameters
Lets make 14GB/5cores on main vm where we build and 8GB/3cores on stanard ones and put max 2 deployment jobs per jenkins slave. Change-Id: I70914f1dde12ab501bba8d0ac957be624f08c0c9
This commit is contained in:
parent
7329cd7f32
commit
067717a8a3
|
@ -48,6 +48,10 @@ export IMAGE_PATH="/home/jenkins/workspace/cloud-images/default-image.qcow2"
|
||||||
export DONT_DESTROY_ON_SUCCESS=1
|
export DONT_DESTROY_ON_SUCCESS=1
|
||||||
export DEPLOY_METHOD="kargo"
|
export DEPLOY_METHOD="kargo"
|
||||||
export SLAVES_COUNT="3"
|
export SLAVES_COUNT="3"
|
||||||
|
export ADMIN_NODE_CPU=5
|
||||||
|
export ADMIN_NODE_MEMORY=14336
|
||||||
|
export SLAVE_NODE_CPU=3
|
||||||
|
export SLAVE_NODE_MEMORY=8192
|
||||||
export WORKSPACE="/home/jenkins/workspace"
|
export WORKSPACE="/home/jenkins/workspace"
|
||||||
export FUEL_DEVOPS_INSTALLATION_DIR=${FUEL_DEVOPS_INSTALLATION_DIR}
|
export FUEL_DEVOPS_INSTALLATION_DIR=${FUEL_DEVOPS_INSTALLATION_DIR}
|
||||||
export CUSTOM_YAML='hyperkube_image_repo: "${HYPERKUBE_REPO}"
|
export CUSTOM_YAML='hyperkube_image_repo: "${HYPERKUBE_REPO}"
|
||||||
|
|
|
@ -33,7 +33,7 @@
|
||||||
concurrent: true
|
concurrent: true
|
||||||
properties:
|
properties:
|
||||||
- heavy-job:
|
- heavy-job:
|
||||||
weight: 2
|
weight: 3
|
||||||
- throttle:
|
- throttle:
|
||||||
option: project
|
option: project
|
||||||
max-per-node: 1
|
max-per-node: 1
|
||||||
|
|
Loading…
Reference in New Issue