On Mon, Mar 30, 2015 at 2:22 PM, Kanstantsin Shautsou <[email protected]> wrote: >>> DumbSlave is not compatible with this strategy is also under >>> question, for example i want accept only one job and then delete DumbSlave. >> >> This makes no sense. You would have to manually go and create a new >> slave after every build. Who would do that? > > Why should i do it manually if strategy exist and i can use it?
Maybe you did not understand what I said. If you have a DumbSlave with an OnceRetentionStrategy, as soon as it runs its first build it will be removed. Since dumb slaves have to be explicitly added, this would be silly. So even offering this retention strategy on a dumb slave would be very confusing to a user. >>> Some users wants to have 2 executers on slave >> >> Then they should not be using OnceRetentionStrategy. > > This reason is not technical It is certainly technical. This strategy is written to support one use case: when the build finishes, the slave is deleted. Any other behavior would require a different implementation. > Should i create another one strategy that will be not limited with executors > number but support durable execution? If you want one. I know of no use case for one, since the usual alternative strategy for cloud slaves is to delete the slave once it has been idle for some time, which does not need to check for ContinuableExecutable that I can see. -- 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/CANfRfr3_OHBO2wBDezs_TF5Fty87Nf-u-3WKLoWmiC6%2Btvbi7g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
