-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins 2.150.2
EC2 plugin didn't noticed that Jenkins is in Shutdown mode and continued started instances (because jobs were in queue) and stopping instances (because jobs weren't started again) and starting, and stopping them again, and on, and on...
This caused $500 bill in Amazon over ~18 hours, because the instances were Windows (m5.xlarge), you pay for full hour and the timeout of inactive instances was set to 1 minute.
Implementation suggestion: If Jenkins is in shutdown mode, don't start new instances.
[JENKINS-56443] EC2 plugin doesn't take into account 'shutdown mode' of Jenkins
Perrin Morrow
added a comment - I raised pull request #337 for this. It has already been merged. 
FABRIZIO MANFREDI
added a comment - merged, it will part of the 1.43 
We've been bitten by this a few times too. I'm currently running a patched version of the plugin that doesn't start instances when in quiet down mode.
It's working fine but I also have other experimental changes on the branch I'm using and I don't have time to test this change in isolation. I am happy to create a branch/PR with just this change on it if someone else can test it.