Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41015

Cannot abort input step anymore in Console Output

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      With a recent upgrade of plugins I can no longer abort Pipelines waiting on an input step.

      See the attached screenshot, but basically hitting the Abort link hits a 404 endpoint.

      The screenshot was after a resumed Pipeline, but I can also reproduce this with a simple input step, e.g.:

      node {
        stage('Build') { sh 'echo "Hi"' }
        stage('Deploy') {
          input message: 'Deploy?', ok: 'Ship It!'
        }
      }
      

        Attachments

        1. about.md
          18 kB
        2. console-output.har
          448 kB
        3. console-output-network.png
          console-output-network.png
          185 kB
        4. Selection_043.png
          Selection_043.png
          56 kB

          Activity

          Hide
          carlosrodlop Carlos Rodríguez López added a comment - - 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

           

           

           

          Show
          carlosrodlop Carlos Rodríguez López added a comment - - 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      
          Hide
          abayer Andrew Bayer added a comment -

          Seems to be working for me with pipeline-input-step 2.8 and core 2.89.3.

          Show
          abayer Andrew Bayer added a comment - Seems to be working for me with pipeline-input-step 2.8 and core 2.89.3.
          Hide
          ganeshpr Ganesh Murthy added a comment -

          I am able to reproduce this issue with pipeline-input-step 2.10 and pipeline 2.6.

          Show
          ganeshpr Ganesh Murthy added a comment - I am able to reproduce this issue with pipeline-input-step 2.10 and pipeline 2.6.

            People

            • Assignee:
              cloudbees CloudBees Inc.
              Reporter:
              rtyler R. Tyler Croy
            • Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: