I am not sure what the concerns surrounding corner cases are, but if the issue is simply that for a build which was loaded from disk (not started in this session) for which we did not independently load the FlowExecution, that ReplayAction.isEnabled is returning false because WorkflowRun.Owner.getOrNull is returning null for reasons of laziness, then the fix is simple: make the action enabled whenever we have a FlowExecutionOwner, and if and when the user invokes the action, then call get() (blocking), check RUN_SCRIPTS for non-sandbox mode, and provide some sort of UI notification if these preconditions are not met. Could all happen in ReplayAction/index.jelly in fact.
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.