-
Bug
-
Resolution: Fixed
-
Major
-
2 jenkins masters:
production1.<fqdn>
cloud:
Name: "jenkins_base"
Project ID: <project_for_gce_slaves>
Instance Cap: 80
Name Prefix: "production1-st2-bionic"
production2.<fqdn>
cloud:
Name: "jenkins_base"
Project ID: <project_for_gce_slaves>
Instance Cap: 10
Name Prefix: "production2-st4-trusty"
Masters version: LTS 1.121.1
gce Plugin version: 1.0.42 jenkins masters: production1.<fqdn> cloud: Name: "jenkins_base" Project ID: <project_for_gce_slaves> Instance Cap: 80 Name Prefix: "production1-st2-bionic" production2.<fqdn> cloud: Name: "jenkins_base" Project ID: <project_for_gce_slaves> Instance Cap: 10 Name Prefix: "production2-st4-trusty" Masters version: LTS 1.121.1 gce Plugin version: 1.0.4
Hi!
We have one google project (for google-compute-engine-plugin) for a several jenkins masters.
Each jenkins master has url "<master_name>.<fqdn>" and each google plugin "Name Prefix" parameter "<master_name><Short_Machine_Type><OS_Type>"
I set "Instance Cap: 10" on one jenkins master and builds are in queue for a long time.
When i opened google project, i saw 15 running instances of other jenkins masters.
But in current jenkins master log file i see:
"Jul 16, 2018 11:22:25 AM com.google.jenkins.plugins.computeengine.ComputeEngineCloud provision
WARNING: Could not provision new nodes to meet excess workload demand (7). Cloud provider jenkins_base has reached its configured capacity of 10 "
When i changed "Instance Cap" to 70, all builds started running and queue were empty.
Can you change logic of "Instance Cap" parameter?
We want to limit "Instance Cap" for jenkins master, not for Google Project.
