Note that you could trigger a background load if and when someone calls getOrNull (but return null for now). Whether or not that is too late depends on the caller. In the case of Replay, it would mean that the action would not initially appear in the sidebar, but then it would appear in the context menu a moment later. For PipelineTimings and JobPropertyStep, this would not really help—in both cases it probably makes more sense to just use get and block if necessary. And I think the originally suggested change to ReplayAction (+ its index.jelly) would be desirable anyway—more transparent to have the link always be there, and if it cannot be used, explain why.
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.