I face the same issue with Mesos and my understanding is that there is a way to declare slaves as *ephemeral* i.e.they will never come back once they are gone. This appeared to be something that the cloud provider plugin (mesos in this case) needs to worry about.
On Thursday, May 25, 2017 at 7:11:57 PM UTC+5:30, Michal Tekel' wrote: > > Hi, > > I have a question if it is possible to configure Jenkins to resume > pipeline build (e.g. after Jenkins restart) on any slave which has required > labels. Currently jenkins will only try to resume on the exactly same build > slave the pipeline was running on before. But sometimes, this slave is > never coming back (e.g. it was a mesos slave and the task is expired). Such > jobs can then never resume, even though jenkins has enough build slaves of > required type available after restart. > > Thanks, > > Michael > -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4ed72f0c-e3dc-479a-9b61-effdcdb71842%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
