It's not a Jenkins problem per-se, it's about how to use an interactive script in non-interactive mode.
There are some ideas here: https://askubuntu.com/questions/439432/passing-arguments-to-an-interactive-script-which-will-run-in-background On 11/29/18, 2:00 PM, "[email protected] on behalf of Adam von Nieda" <[email protected] on behalf of [email protected]> wrote: I’ve got to run a bash script via Jenkins, and it expects several input values / carriage returns. Before I go down a rabbit hole, is there some standard way to handle something like this within Jenkins? I’d be running this as a pipeline stage. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/A69A628C-FAE7-42F4-BD60-36D46133F1AC%40godaddy.com. For more options, visit https://groups.google.com/d/optout.
