Hello dear developers and maintainers,

In order to keep our infrastructure's costs under an acceptable bar 
(https://issues.jenkins.io/browse/INFRA-3097 for AWS), we are setting up 
ci.jenkins.io's agents to use spot instances.

*TL;DR;* 
- If you see your builds failing because the agent (either VM or container, 
Linux or Windows) has been stopped, please let us know by answering to this 
email with a link to the failed job, and eventually adding logs for context.
  * In such case, you have to start a new build to ensure success... for 
now.

*Details*
Spot instances are cloud instances (e.g. virtual machines) at low prices 
comapred to the usual VMs instances.
Their low prices comes from the fact that these instances can be reclaimed 
and stopped at any moment because it runs on unused infrastructure that can 
be requested at any moment. It means that the "spot" based agents can be 
reclaimed at any moment: in this case, the VM is properly stopped in less 
than 2 minutes.

Of course, if you have a build running on a reclaimed machine, the build 
will fail. There are numerous solutions but none is available out of the 
box. One of the long term solution would be a pipeline feature to 
automatically restart a build step that failed because of an agent outage, 
since 
https://github.com/jenkinsci/workflow-durable-task-step-plugin/pull/176 
allowed to report such a failure cause.

On the short term, we are checking if these failures are happening "for 
real" given the short time span of our agents: if it causes trouble we'll 
try to leverage by mixing spot/non-spot or splitting per build types if 
some builds are more prone to fails because of spot eviction.

Thanks for your understanding!

For the Jenkins Infra team, Damien

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/02372f5f-774a-41ad-9bd1-01ca861fd7ean%40googlegroups.com.

Reply via email to