Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
What do you want us to build?
Add Mixed Instance and Purchase Options support to Buildkite ASG
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
This will enable the customers to launch and automatically scale a fleet of on-Demand Instances and Spot Instances within a single ASG to run the CI jobs. With this one or more instance types can also be specified which will override the default instance type specified in the launch template.
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
Community Note
Tell us about your request What do you want us to build? Add Mixed Instance and Purchase Options support to Buildkite ASG
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
This will enable the customers to launch and automatically scale a fleet of on-Demand Instances and Spot Instances within a single ASG to run the CI jobs. With this one or more instance types can also be specified which will override the default instance type specified in the launch template.
Are you currently working around this issue? How are you currently solving this problem? https://github.com/buildkite/elastic-ci-stack-for-aws/pull/651
Additional context Anything else we should know?
Attachments If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)