Lease Time

[fubian]

What feature do you want to see added?

The lockable resources shall have a lease time. If it is used e.g. for a license, that license would be blocked during the execution of the job + the lease time. If that additional time is not considered in the lockable resources, the license cannot be checked out in another node than the one before.

Upstream changes

No response

Are you interested in contributing this feature?

No response

[mPokornyETM]

I am not sure, what you mean. Can you provide more description, wished scenario (code)
What you exactly mean with " license cannot be checked"? What should happen? Skip the execution of the scope. Or lockt the resource for ? How long? Who and where shall decide the additional lease time.

[onionmad]

I think what is ment is that we would want a way to be able to exit the locked section in your groovy code, but keep the resource locked for a defined amount of time, as to not stall pipelines that use licenses with cooldown periods, etc (as would be the case when simply using a wait timer within the lock section itself).

I +1 this request.

[mPokornyETM]

I think what is ment is that we would want a way to be able to exit the locked section in your groovy code, but keep the resource locked for a defined amount of time, as to not stall pipelines that use licenses with cooldown periods, etc (as would be the case when simply using a wait timer within the lock section itself).

I +1 this request.

then somethink like this, where the delay is time in miliseconds.

lock(resource: licenseServer1, onReleaseDelay : 500, onCancelDdelay : 0])

right?

[onionmad]

I think what is ment is that we would want a way to be able to exit the locked section in your groovy code, but keep the resource locked for a defined amount of time, as to not stall pipelines that use licenses with cooldown periods, etc (as would be the case when simply using a wait timer within the lock section itself).
I +1 this request.

then somethink like this, where the delay is time in miliseconds.

lock(resource: licenseServer1, onReleaseDelay : 500, onCancelDdelay : 0])

right?

That looks good. Though our current license has 5 minutes of cooldown, so maybe the units should be in seconds.
Also, I would like to emphasize that the onReleaseDelay reaction should be a background activity, not blocking any subsequent pipeline actions (unless they rely on the resource that remains locked for onReleaseDelay).

[mPokornyETM]

e onReleaseDelay reaction should be a background activity

and exactly this will be chalange for me. But we have clarifeid it now, so I will accept this feature and push it in our 'small' backlog