Feature request: Support Capacity Providers

Amazon recently made Fargate Spot generally available. What it basically does is run Fargate tasks in an EC2 Spot Instance-esque fashion, while greatly reducing the cost to run them. This seems like a match made in heaven for running certain Jenkins jobs at an extremely attractive price.

What we’d need to do is support the specification of Capacity Providers when defining Cloud Provider Templates. That could look similar to Placement Strategies field in the current implementation.

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-capacity-providers.html

[owengo]

if some want to test/need to launching tasks via the default capacity provider I did a quick hack at: https://github.com/owengo/amazon-ecs-plugin in “launchType” if you choose “Default Capacity Provider” instead of “EC2” or “Fargate” the “runTask” call will not pass a launchType and so the default capacityProvider for your cluster will be used. “works for me”.

[sithmein]

I believe a minimal first step would be to make the the launchType optional (in com.cloudbees.jenkins.plugins.amazonecs.ECSService.runEcsTask). According to the latest AWS docs if you omit the launch type and the capacity provider when submitting a task the default capacity provider is chosen. So you can configure everything in ECS and simply “disable” the launch type in Jenkins. This should be a trivial change. If this is of interest I can even work on a PR for this.