Tried to re-use RetentionStrategy jelly chooser code and was surprised that not all strategies found by descriptor lookup.Is there any reason why CloudRetentionStartegy and OnceRetentionStartegy has do descriptors and ui config page?
What will happen if i will use OnceRetentionStartegy with >1 executor number?
What will happen if i will use other retention strategies instead of Cloud strategies, i.e. Always? Should i expect that it will run slaves according to available limits and keep them always online?
This sounds weird, but in theory it may work in docker-plugin like any DumbSlave and provide end-users ability to create different configurations.
--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/92fa961b-6147-4866-a47a-51926c1ea4c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
OnceRetentionStrategy has no descriptor because it makes no sense to select on a static slave, and clouds generally hardcode the desired strategy.
It cannot be used with multiple executors, that would make no sense either.
OnceRetentionStrategy has no descriptor because it makes no sense to select on a static slave, and clouds generally hardcode the desired strategy.
It cannot be used with multiple executors, that would make no sense either.
On Mon, Mar 30, 2015 at 2:22 PM, Kanstantsin Shautsou
<kanstan...@gmail.com> 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.