The most idiomatic way to use input result values in pipeline model script is to set it as an (environment) variable which subsequent steps or stages can use.
Pipeline model doesn't have explicit variables, so this is likely the only way.
This is a problem in both Declarative Pipeline and Pipeline Script. We need to solve the underlying problem for both
Which means solving it in the input step, since we'll get whatever benefits from that for free elsewhere.
Switching this over to JENKINS-38394 which is a more general-purpose version of this.
Patrick Wolf Andrew Bayer don't you think this is worth solving for both?
Bulk closing resolved issues.