[JIRA] [ec2-plugin] (JENKINS-32469) Allow falling back to on demand when spot prices are higher then limit.

2 views
Skip to first unread message

kim@trikeapps.com (JIRA)

unread,
Jan 14, 2016, 11:41:02 PM1/14/16
to jenkinsc...@googlegroups.com
kim Dowling created an issue
 
Jenkins / New Feature JENKINS-32469
Allow falling back to on demand when spot prices are higher then limit.
Issue Type: New Feature New Feature
Assignee: Francis Upton
Components: ec2-plugin
Created: 15/Jan/16 4:40 AM
Priority: Minor Minor
Reporter: kim Dowling

It would be very nice to have a options of falling back to using on demand instances when the Spot price is above the set Bid Price.

We currently only use EC2 on demand instances for our Jenkins slaves and would love to be able to use spot instances but do not want a situation where no slaves get spun up because the spot price is too high.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

lee@britecore.com (JIRA)

unread,
Mar 16, 2016, 12:59:01 PM3/16/16
to jenkinsc...@googlegroups.com
Lee Hicks commented on New Feature JENKINS-32469
 
Re: Allow falling back to on demand when spot prices are higher then limit.

We are having the same issue too. Spot pricing spikes crazy leaving our builds pending.

lee@britecore.com (JIRA)

unread,
Mar 16, 2016, 1:00:03 PM3/16/16
to jenkinsc...@googlegroups.com
Lee Hicks edited a comment on New Feature JENKINS-32469
We are having the same issue too. Spot pricing spikes crazy leaving our builds pending.


Been thinking about how to tweak the plugin but Java isn't my strong suite nor is the Jenkins codebase.

shields@kkvesper.jp (JIRA)

unread,
May 7, 2016, 10:22:01 PM5/7/16
to jenkinsc...@googlegroups.com

Here's how I would implement this:

1) Add new boolean flag "fallbackToOndemand" for spot instances.

2) When lauching instances, if "fallbackToOndemand" do a spot price check to see whether to use spot or ondemand, and call the appropriate class. I believe this is in SlaveTemplate class , provision() method.

3) EC2RetentionStrategy is responsible for killing instances. Here you'll have to do periodic spot price check for any "fallback ondemand" instances to see if the spot price has come back down, in which case you can kill the ondemand and allow a spot to be restarted in it's place (it will pass the check in #2)

4) You may want to add some mechanism to prevent constant toggling between ondemand and fallback. At least you should not change more frequently that 1 hour, because you pay for a minimum of 1 hour usage even if you use less than one hour.

brian.melanson@he360.com (JIRA)

unread,
Nov 15, 2018, 4:45:03 PM11/15/18
to jenkinsc...@googlegroups.com

Agree, this would be a very useful feature, useful in this situation (https://issues.jenkins-ci.org/browse/JENKINS-39283

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

brian.melanson@he360.com (JIRA)

unread,
Nov 15, 2018, 4:46:02 PM11/15/18
to jenkinsc...@googlegroups.com
Brian Melanson edited a comment on New Feature JENKINS-32469
Agree, this would be a very useful feature, useful in this situation (https://issues.jenkins-ci.org/browse/JENKINS-39283 )   , often because a spot instance of a certain type is unavailable for allocation.

raihaan.shouhell@autodesk.com (JIRA)

unread,
Jun 26, 2019, 12:04:02 PM6/26/19
to jenkinsc...@googlegroups.com

This should be resolved in the latest version could people test that

raihaan.shouhell@autodesk.com (JIRA)

unread,
Jul 29, 2019, 5:09:02 AM7/29/19
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages