[JIRA] (JENKINS-61363) Missbehavior on 'Minimum number of instances' and 'Minimum number of spare instances'

[anufriev.o.m@gmail.com (JIRA)]

Oleg Anufriev created an issue

Jenkins / JENKINS-61363 Missbehavior on 'Minimum number of instances' and 'Minimum number of spare instances' Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-03-06 10:54 Environment: Jenkins ver. 2.223 ec2 plugin ver. 1.49.1 Priority: Major Reporter: Oleg Anufriev I have configured 2 AWS clouds in different regions with 1 AMI in each (with different names) It said that 'Minimum number of spare instances' and 'Minimum number of instances' act on per AMI basis. I observe behavior like these settings are global for the whole plugin. Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[anufriev.o.m@gmail.com (JIRA)]

Oleg Anufriev updated an issue

Jenkins / JENKINS-61363 Missbehavior on 'Minimum number of instances' and 'Minimum number of spare instances'

Change By: Oleg Anufriev I have configured 2 AWS clouds , for example (prodVpc and devVpc) in different regions with 1 AMI in each (with different names)

It said that 'Minimum number of spare instances' and 'Minimum number of instances' act on per AMI basis.

I observe behavior like these settings are global for the whole plugin and mean total of ec2 slaves independently of cloud and AMI . Configuring: Minimum number of instances=1 Minimum number of spare instances=1 for each ami/cloud i've expected to get 2 ec2 slaves in total: 1 for prodVpc and 1 for devVpc. I get only one ec2 slave instead.

Add Comment

[anufriev.o.m@gmail.com (JIRA)]

Oleg Anufriev updated an issue

Jenkins / JENKINS-61363 Missbehavior on 'Minimum number of instances' and 'Minimum number of spare instances' Change By: Oleg Anufriev

I have configured 2 AWS clouds, for example (prodVpc and devVpc) in different regions with 1 AMI in each (with different names)

It said that 'Minimum number of spare instances' and 'Minimum number of instances' act on per AMI basis. I observe behavior like these settings are global for the whole plugin and mean total of ec2 slaves independently of cloud and AMI. Configuring: Minimum number of instances=1 Minimum number of spare instances=1 for each ami/cloud i've expected to get 2 ec2 slaves in total: 1 for prodVpc and 1 for devVpc. I get only one ec2 slave instead.

When i run pipeline, that requires absent slaves plugin  fires them up successfully.

Add Comment

[anufriev.o.m@gmail.com (JIRA)]

Oleg Anufriev updated an issue

Jenkins / JENKINS-61363 Missbehavior on 'Minimum number of instances' and 'Minimum number of spare instances' Change By: Oleg Anufriev

I have configured 2 AWS clouds, for example (prodVpc and devVpc) in different regions with 1 AMI in each (with different names) It said that 'Minimum number of spare instances' and 'Minimum number of instances' act on per AMI basis. I observe behavior like these settings are global for the whole plugin and mean total of ec2 slaves independently of cloud and AMI. Configuring: > Minimum number of instances=1 > Minimum number of spare instances=1 for each ami/cloud i've expected to get 2 ec2 slaves in total: 1 for prodVpc and 1 for devVpc. I get only one ec2 slave instead.

When Changing these parameters values up and down and running jobs i run pipeline 've made a conclusion , that requires absent slaves plugin   fires them takes in account the total number of fired up successfully by plugin instances, regardless to Cloud name or AMI id .

Add Comment