-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Master spot instances #54735
Master spot instances #54735
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably do this in sre jenkins? Specially now that we have a master branch off of 2019.2.1?
Yeah, we'll have to do it there too. We'll need it here too for PR's. |
I realized we also need to reduce the timeout from 6 hours to something like 5 hours and 45 minutes so that we can still attempt to download artifacts if it times out. |
re-run full all |
23a14eb
to
fcae32f
Compare
@s0undt3ch Can we extend the startup time for the multi-master test and then just leave centos 7 out of spot instances and leave it on a c5.xlarge or something? |
I'd say yes to all accounts. |
23fe8b7
to
1c8678a
Compare
re-run debian9 |
8554a0d
to
6be4d8d
Compare
740b4fb
to
aaadc9b
Compare
re-run opensuse15 |
re-run centos7 |
re-run fedora29 |
re-run macosxmojave |
re-run windows2019 |
What does this PR do?
It uses spot instances if they are available at the moment
Previous Behavior
We always used on-demand instances
New Behavior
It attempts to use a spot instance before trying an on-demand instance
Commits signed with GPG?
Yes