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

Proceed or Abort redirecting to job console page and do not perform their function

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • None
    • Jenkins v 2.414.3 ; Input Step plugin v 477.v339683a_8d55e ; Blue Ocean plugin v 1.27.8
      Docker community: 24.0.5

      The Proceed or Abort links contained in a DSL declarative pipeline job do not perform their function from the main jenkins job console. Their links appear to link back to the job console page itself and neither allow the job to proceed nor abort.

      If you switch to Blue Ocean, these functions do work.

      The Root URL issue does not appear to be the cause here.

          [JENKINS-72237] Proceed or Abort redirecting to job console page and do not perform their function

          Steve created issue -
          Steve made changes -
          Description Original: The Proceed or Abort links contained in a DSL declarative pipeline job do not perform their function from the main jenkins job console. Their links appear to link back to the job console page itself and neither allow the job to proceed nor abort.

          If you switch to Blue Ocean, these functions do work
          New: The Proceed or Abort links contained in a DSL declarative pipeline job do not perform their function from the main jenkins job console. Their links appear to link back to the job console page itself and neither allow the job to proceed nor abort.

          If you switch to Blue Ocean, these functions do work.

          The Root URL issue does not appear to be the cause here.
          Naveen Boni made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Mark Waite added a comment -

          I can't duplicate the behavior on my Jenkins controller that does not have Blue Ocean installed.  My declarative Pipeline correctly proceeded or aborted from the console log. Maybe the case is specific to having the Blue Ocean plugins installed?

          My declarative Pipeline job looked like this:

          pipeline {
              agent none
              stages {
                  stage('Hello and Goodbye') {
                      input {
                          message 'Shall we proceed with the first greeting?'
                          ok 'Yes, greet me first'
                      }
                      steps {
                          echo 'Hello World'
                          input message: 'Shall we proceed with the second greeting?', ok: 'Yes, please greet me again'
                          echo 'Goodbye World'
                      }
                  }
              }
          }
          

           

          Does the failure happen when you do not have Blue Ocean installed?

          Mark Waite added a comment - I can't duplicate the behavior on my Jenkins controller that does not have Blue Ocean installed.  My declarative Pipeline correctly proceeded or aborted from the console log. Maybe the case is specific to having the Blue Ocean plugins installed? My declarative Pipeline job looked like this: pipeline { agent none stages { stage( 'Hello and Goodbye' ) { input { message 'Shall we proceed with the first greeting?' ok 'Yes, greet me first' } steps { echo 'Hello World' input message: 'Shall we proceed with the second greeting?' , ok: 'Yes, please greet me again' echo 'Goodbye World' } } } }   Does the failure happen when you do not have Blue Ocean installed?

          Mark Waite added a comment -

          naveenboni was there a reason that you listed this issue as "in progress"? Are you investigating it or trying to duplicate it?

          Mark Waite added a comment - naveenboni  was there a reason that you listed this issue as "in progress"? Are you investigating it or trying to duplicate it?

          Anvesh added a comment -

          Helo markewaite naveenboni , I am facing the same issue with Jenkins 2.426.1. Did you find any solution for this?

           

          Anvesh added a comment - Helo markewaite naveenboni , I am facing the same issue with Jenkins 2.426.1. Did you find any solution for this?  
          Mark Waite made changes -
          Summary Original: Proceed or Abort redirecting to job console page and do not perform there fcuntion New: Proceed or Abort redirecting to job console page and do not perform their function
          Mark Waite made changes -
          Attachment New: run-jenkins.sh [ 61615 ]
          Mark Waite made changes -
          Attachment New: plugins.txt [ 61616 ]

          Mark Waite added a comment -

          anvesh_gummala I didn't find a solution for this because I cannot duplicate the problem.

          Can you describe the precise steps you take to duplicate the problem on a fresh installation of Jenkins?

          I took the following steps and was unable to duplicate the problem:

          1. Create a plugins.txt file that defines the exact plugins and versions I am using
          2. Create a run-jenkins.sh that runs Jenkins 2.414.3 with the plugins defined in plugins.txt
          3. Run the run-jenkins.sh script and complete the setup wizard by choosing to install no additional plugins
          4. Define a declarative Pipeline job as noted in my earlier comment (two input steps)
          5. Run the declarative Pipeline job from the "Build now" link (outside Blue Ocean) and confirm that each path through the input behaves as expected from the console log
          6. Run the declarative Pipeline job from the Blue Ocean interface and confirm that the input prompts behave as expected from the Blue Ocean interface

          Unless there is a response from you or from bremnertech, I will likely close this as "Cannot reproduce", since all my attempts to duplicate the issue have failed.

          Mark Waite added a comment - anvesh_gummala I didn't find a solution for this because I cannot duplicate the problem. Can you describe the precise steps you take to duplicate the problem on a fresh installation of Jenkins? I took the following steps and was unable to duplicate the problem: Create a plugins.txt file that defines the exact plugins and versions I am using Create a run-jenkins.sh that runs Jenkins 2.414.3 with the plugins defined in plugins.txt Run the run-jenkins.sh script and complete the setup wizard by choosing to install no additional plugins Define a declarative Pipeline job as noted in my earlier comment (two input steps) Run the declarative Pipeline job from the "Build now" link (outside Blue Ocean) and confirm that each path through the input behaves as expected from the console log Run the declarative Pipeline job from the Blue Ocean interface and confirm that the input prompts behave as expected from the Blue Ocean interface Unless there is a response from you or from bremnertech , I will likely close this as "Cannot reproduce", since all my attempts to duplicate the issue have failed.

            Unassigned Unassigned
            bremnertech Steve
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: