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

Starting and stopping existing instances

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Fixed but Unreleased (View Workflow)
    • Priority: Major
    • Resolution: Won't Do
    • Component/s: ec2-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      Hello,

      We use Terraform and Chef to provision and configured all Jenkins slaves. Therefore the provision part of the plugin is not essential for us. We are more interested in starting and stopping existing instances based on the load of the cluster using our own instances.

      If possible, please add the functionally to scale the cluster using existing instances:

      • add a field to configure a list of existing instances (or a tag)
      • start instances from the predefined list (or from the list of instances having the same tag)
      • don't do nothing else except of changing the instance state to start or stop

      Thank you. 

        Attachments

          Activity

          Hide
          thoulen FABRIZIO MANFREDI added a comment -

          Hi ,

          At the moment we have several bugs to fix, I am not sure when I can implement that.

          In the mean time Jenkins is already able to recover disconnected nodes not registered, you have to use the right tags to the instances, those nodes are considered orphans and automatically reconnected (and restarted) before any new nodes.

          I am not sure what happen if you remove the nodes with Terraform/chef , if Jenkins is able to remove as well or if it stay as broken node.

           

          Another option you can run groovy script that is checking the account and create the configuration in jenkins for the nodes.

          Show
          thoulen FABRIZIO MANFREDI added a comment - Hi , At the moment we have several bugs to fix, I am not sure when I can implement that. In the mean time Jenkins is already able to recover disconnected nodes not registered, you have to use the right tags to the instances, those nodes are considered orphans and automatically reconnected (and restarted) before any new nodes. I am not sure what happen if you remove the nodes with Terraform/chef , if Jenkins is able to remove as well or if it stay as broken node.   Another option you can run groovy script that is checking the account and create the configuration in jenkins for the nodes.
          Hide
          danielstoian Daniel Stoian added a comment -

          Ok. Thank you.
          We will go with a groovy script option.

          Show
          danielstoian Daniel Stoian added a comment - Ok. Thank you. We will go with a groovy script option.

            People

            • Assignee:
              thoulen FABRIZIO MANFREDI
              Reporter:
              danielstoian Daniel Stoian
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: