Minimum Instances In the Cluster Should Be Zero When No Jobs Are Scheduled

[dinusha92]

Description:

Jenkins ECS cluster should contain at least one instance in the cluster. Otherwise when a build job is triggered, the container cannot see any instances in the cluster. Hence it would not be able to deploy in the cluster. In this approach we have to pay an instance for 24*7 even if it's not used always.

Suggestion is to keep the minimum instances to zero and write a script to call Jenkins APIs and get the length of build queue and if there is any job in the queue and if there are no instances in the cluster, then an EC2 instance with the relevant launch configuration would be created in the cluster using AWS APIs.
Suggested Labels:

Improvement
Suggested Assignees:

Dinusha Dissanayake, KasunG Gajasinghe, Harshan Liyanage
Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues: