Feature: Configurable timeout for child task startup in CTR

[Clemens-L]

trafficstars

Allows the configuration of a timeout for the startup of child tasks (max-start-wait-time) in the Composed Task Runner that can be smaller than the timeout for task completion (max-wait-time).

To check whether a child task is still in startup, we check whether the start time of the taskExecution has been set:

(taskExecution == null || taskExecution.getStartTime() == null)

This has been very helpful in our application, where we have some very long running tasks. By setting a max-start-wait-time that is significantly smaller than the max-wait-time, we can react a lot faster to tasks that fail on startup (for example, due to application context initialization failures).

[onobc]

HI @Clemens-L I just wanted to reach out to let you know that we see your contribution and will get to it asap after we get the 2.11.2 release out. Thanks for your patience.

[Clemens-L]

Sounds good, thanks! 👍

[cppwfs]

The changes look good. Can you rebase and we'll merge!

[Clemens-L]

Hi @cppwfs, done! Thanks for getting back to this

[cppwfs]

@Clemens-L Thank you soooooo much for this contribution. We apologize for not getting it in sooner. Keep up the great contributions!

I only had to add a small polish on merge so that the option would appear in the UI.

[cppwfs]

LGTM Polish,Squashed, merged Thank you for the contribution!!!