As part of JENKINS-32986 pipeline cps plugin has introduced a 5 min timeout for each instruction on the script.
Custom scripts that are implemented as jenkins.tasks.BuildWrapper are now subject to this limitation.
As BuildWrappers are a very useful and common extension point it seems to me that Jenkins administrators should be able to increase this hard coded timeout by passing a configuration (maybe a -D vm param)
OR (even better) developers that are writing Build wrappers can provide something like a max timeout hint to cps treat it properly (maybe by implementing an interface or an annotation).
This change on behavior from 2.4 to 2.5 pipeline jenkins broke our plugin on some use cases.
As DurableSteps (that are not subject to this limitation) are "steps" not "wrappers" I cannot see how to change our implementation to some structure that acts as a wrapper without touch the 5 min limitation.