ec2-fleet-3.0.0

What's Changed

🚀 What’s New?

• oldId is no longer used and nodes & computers are no longer re-assigned to the new cloud objects (after configuration save) because they have been causing numerous hard-to-debug issues. The tracking of clouds that the nodes & computers belong to is instead done using cloud name.
• Cloud name:
  • Is required
  • Jenkins Cloud names are validated for uniqueness. Error messages are displayed in the UI for non-unique names used.
    
  • UI: unique cloud names are unmodifiable and a unique default name is suggested for new clouds e.g. FleetCloud-QXlsET6X
  • JCasC: users can now ask plugin to generate a unique default cloud name by specifying “” for name.

🐛 Bug Fixes

• #360 #322 Remove references of oldId and EC2FleetCloudAware class, remove tracking of cloud objects. Replaced cloud object tracking with tracking by name making cloud name a special configuration
• #397 MaxTotalUses didn't show the correct value in the UI, instead showed the default -1.
• #335 Resubmitted build uses the parameters of the last failed build instead of the last build

📓 Others

• Minor refactoring:
  • Renamed FleetNode#name to instanceId for clarity, added getDescriptor to return sub type
  • Added a check to not provision if Jenkins is quieting down or terminating
• Updated documentation
• Added AWS's warning about SpotFleet usage to ReadME.

✅ PRs

• #383
• #390
• #392
• 
#395

• #403

• #394
• #388
• #401
• #402
• #404

🗒️ Upgrade Steps

This release changes the way clouds and their agents are tracked in a backwards incompatible way. The following changes to cloud configurations are required:

• JCasc users:
  Fix configuration and reload configuration under Manage Jenkins -> Configuration as Code
  • remove usage of oldId, it is no longer used
  • make cloud names unique. JCasc users can ask plugin to name their clouds by specifying name: "" (Tip: Use the UI to identify clouds with duplicate names)
• UI users:
  • rename clouds with non-unique name
  • optionally, use dynamically generated default for new clouds

🤝 Thanks to the contributors for reporting issues and sharing helpful information:

🌟 @wzur-r3, @wosiu, @mwos-sl, @icep87, @limasilet, @benipeled, @tim-goto, @decoursin, @fluffysquirrels, @roded
🌟 @vineeth-bandi's first contribution

Full Changelog: ec2-fleet-2.6.0...ec2-fleet-2.7.0