Carlos Rodríguez López added a comment - 2017-10-02 14:10 - edited Similar Behaviour observed but getting a 405 (not 404), see section Result > JS Debug Console Environment  See attached about.md Jenkinsfile   stage( 'Test' ) { node { echo "hi" } try { timeout(time:2, unit: 'MINUTES' ) { input message: "Ready to publish?" , ok: 'Publish' } } finally { node { echo "bye" } } } Result Input options via Console Output does not work JS Debug Console VM5689:1 OPTIONS http: //127.0.0.1:8080/job/test1-Scripted_bug/7/input/D8cfa70e6608717c08486ae3035ac018/proceedEmpty net::ERR_ABORTED (anonymous) @ VM5689:1 request @ prototype.js:1585 initialize @ prototype.js:1550 (anonymous) @ prototype.js:452 klass @ prototype.js:101 onclick @ console:1 console:1 Failed to load http: //127.0.0.1:8080/job/test1-Scripted_bug/7/input/D8cfa70e6608717c08486ae3035ac018/proceedEmpty: Response to preflight request doesn 't pass access control check: No ' Access-Control-Allow-Origin ' header is present on the requested resource. Origin ' http://localhost:8080' is therefore not allowed access. The response had HTTP status code 405. JS Debug  Network Addtional notes Using other methods like Input menu (`<JENKINS_URL>/<PIPELINE_JOB>/<BUILD_NUMBER>/input/`) or Pipeline Stage View works HAR.file attached      

Andrew Bayer added a comment - 2018-02-23 21:59 Seems to be working for me with pipeline-input-step 2.8 and core 2.89.3.

Ganesh Murthy added a comment - 2019-07-11 21:48 I am able to reproduce this issue with pipeline-input-step 2.10 and pipeline 2.6.

Seph Soliman added a comment - 2022-07-28 16:55 - edited The issue is still present in Jenkins 2.359 with Pipeline: Input Step, Version 449.v77f0e8b_845c4 installed. The issue is that question marks are not encoded, which is unfortunate given the likelihood that they'll be used during an input (ie. a question is being asked to the user). The questionmark is sent as-is, ie: ...42/input/Deploy%20now ? /abort Which causes the URL to be invalid/stop after "now?" so the important "/abort" part is ignored, hence no action. It should have been: ...42/input/Deploy%20now %3F /abort Which will correctly abort. Ganesh and Tyler: The solution is to avoid using question marks in your input questions. No joke. (This may be the same as  JENKINS-34862  - but an actual bug, not a config issue)

Seph Soliman added a comment - 2022-07-28 21:24 Added PR to fix it: https://github.com/jenkinsci/pipeline-input-step-plugin/pull/112  

James Nord added a comment - 2022-07-29 20:09 - edited Fwiw I think the correct workaround is to add an id to the input step usage so that it does not use the one generated from the message.   Eg   input id: 'publish', message: "Ready to publish?", ok: 'Publish'