Jenkins offlines cloud build slave with running jobs?

[ZillaYT]

I'm using v2.0.2 of https://github.com/jenkinsci/ec2-fleet-plugin

I created spot fleets in AWS to use as Jenkins build slaves, and then in Jenkins configuration, I added an "Amazon EC2 Fleet" to use those build slaves. I set the "Max Idle Minutes Before Scaledown" to 60 mins, and expect that Jenkins to ONLY offline a build slave if no job was running on it for the last 60 mins. However, Jenkins still does offline them. Any fix?

[Slide]

Please use the term "agent" instead of "slave". That term has been deprecated since 2016.

Regards,

Alex

On Mon, Jun 29, 2020 at 7:26 AM ZillaYT <zil...@gmail.com> wrote:

I'm using v2.0.2 of https://github.com/jenkinsci/ec2-fleet-plugin

I created spot fleets in AWS to use as Jenkins build slaves, and then in Jenkins configuration, I added an "Amazon EC2 Fleet" to use those build slaves. I set the "Max Idle Minutes Before Scaledown" to 60 mins, and expect that Jenkins to ONLY offline a build slave if no job was running on it for the last 60 mins. However, Jenkins still does offline them. Any fix?

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/84c079c6-7808-44c1-a9c8-388276c5072eo%40googlegroups.com.

--

Website: http://earl-of-code.com

[Anatoly Utkin]

Might it be you are using spot instances for that?

Then they can really go down randomly and it's expected, it's how AWS EC2 spot instances work.