ec2-fleet-1.17.1

Bugfixes

• Fix infinite loop if describe intances call is failing with exception not related to not found instance #163
  • @jeanblanchard for report

ec2-fleet-1.17.0

Features

• Label based Configuration, beta, PR #160
  • With this feature user of EC2 Fleet Plugin doesn't need to have pre-created AWS resources
    to start configuration and run Jobs. Plugin required just AWS Credentials
    with permissions to be able create resources.
  • How to use https://github.com/jenkinsci/ec2-fleet-plugin/blob/master/docs/LABEL-BASED-CONFIGURATION.md

ec2-fleet-1.16.2

Bugfixes

• Handle EC2 Spot Fleet modifying state correctly. Due to the implementation of each modification of fleet not applied immediately and required some time during which targetCapacity is old. EC2 Spot Fleet Lifecycle #156 #149 CR #159
• Avoid negative target capacity if fleet updated outside of plugin (a few other cases) CR #159
• Fix widget information #147 CR #159

ec2-fleet-1.16.1

Bugfixes

• Take in account number of executors for No Delay Provision Strategy instead of just number of launched EC2 instances, reported in #149
• Add detailed logging into No Delay Provision Strategy

ec2-fleet-1.16.0

🚀 New features and improvements

• Add plugin specific prefix to AWS SDK User Agent (simple debugging) (#150) @terma

ec2-fleet-1.15.0

Featurs

• Support of EC2 Auto Scaling Group as EC2 fleet PR #146
  • Plugin supports two options for now EC2 Spot Fleet and Auto Scaling Groups
    • To start use ASG just go to Plugin configuration and update existent configuration by selecting ASG instead of EC2 Spot Fleet in a list
  • Note If you want to start use ASG make sure that plugin has permissions to use them, check IAM User permissions with updated https://github.com/jenkinsci/ec2-fleet-plugin#setup

ec2-fleet-1.14.0

Features

• Plugin adds tag to all used EC2 instances with ec2-fleet-plugin:cloud-name=<CloudName> tag, for easy search in AWS Console. You can find all resources used by plugin or per cloud. PR #143
  • Not critical, if plugin doesn't have permissions for tags of fail by other reason, tagging will be skipped and plugin will continue operate.

ec2-fleet-1.13.0

Features

• Allow to enable no delay provision strategy PR #142
  • To enable goto configuration and check No Delay Provision Strategy
  • Disable default delay between job scheduled and request additional capacity if existent not enough
  • Note this could lead to additional capacity spikes which improve Jenkins queue throughput but requires sometimes additional capacity. Be careful with Windows

ec2-fleet-1.12.0

Features

• Configurable cloud check interval to avoid AWS API throttling for big amount of fleets in one AWS Account. PR #140
  • Be aware increasing interval will increase delay for scale events. Default is 10 sec if you set it to 60 sec any scale events will happen each 60 sec

ec2-fleet-1.11.2

Bugfixes

• Significant performance and stability upgrade for big fleets or big amount of fleets, details in PR #138
  • details:
    • 35 times drop for a time which Jenkins spend on plugin execution
    • 10% improvement for plugin overall execution time
    • Significant reduction for scale factor, now a plugin requires +2% time for additional +100% load vs +400% time for an old version
    • Zero blockers for Jenkins cycle. Jenkins overall performance is not affected by plugin any more
    • Make amount of calls to AWS EC2 API more predictable (and reduce it). Plugins can make no more than 30 API calls per min.
  • it's marked as bugfix (bugfix version changed) as no new features just performance

Feedback is really welcome, comment #138