[JIRA] (JENKINS-38392) Input step implies that values are set to environment variables when they are not

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title

Andrew Bayer resolved as Won't Fix   So now when you use the new input directive on a stage in Declarative, the parameters actually do end up in the environment. So that's...something? I don't think it's worth dealing with rewriting the core help text to be more vague, so I'd say this is a won't fix. Jenkins / JENKINS-38392 Input step implies that values are set to environment variables when they are not Change By: Andrew Bayer Status: Open Resolved Resolution: Won't Fix Add Comment   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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.