Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-52649

Parameter Instance Cap doesn't work for cloud.

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Labels:
    • Environment:
    • Similar Issues:

      Description

      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.

        Attachments

          Activity

          ramzol dmitrii dudin created issue -
          evanbrown Evan Brown made changes -
          Field Original Value New Value
          Assignee Evan Brown [ evanbrown ] Rachel Yen [ zombiemoose ]
          Hide
          ingwar Karol Lassak added a comment -

          Clouds are distinguished by cloud "Name" field..

          So if you name your clouds with same name in different jenkins instalation (in your case seems its jenkins_base) they will share same pool.

           

          Would be good solution to add that information to help of name field. 

          Show
          ingwar Karol Lassak added a comment - Clouds are distinguished by cloud "Name" field.. So if you name your clouds with same name in different jenkins instalation (in your case seems its  jenkins_base ) they will share same pool.   Would be good solution to add that information to help of name field. 
          Hide
          zombiemoose Rachel Yen added a comment -

          Hmm, good point. I should include that in the help file.

          Show
          zombiemoose Rachel Yen added a comment - Hmm, good point. I should include that in the help file.
          Hide
          zombiemoose Rachel Yen added a comment -

          See this for the logic that dictates how capacity is determined.

          Show
          zombiemoose Rachel Yen added a comment - See this  for the logic that dictates how capacity is determined.
          Hide
          zombiemoose Rachel Yen added a comment -

          Closing this.

           

          If you need to re-open, see: https://github.com/jenkinsci/google-compute-engine-plugin/issues/36

           

          We are migrating off Jira for issues.

          Show
          zombiemoose Rachel Yen added a comment - Closing this.   If you need to re-open, see: https://github.com/jenkinsci/google-compute-engine-plugin/issues/36   We are migrating off Jira for issues.
          zombiemoose Rachel Yen made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              zombiemoose Rachel Yen
              Reporter:
              ramzol dmitrii dudin
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: