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

Error running a manual pipeline step

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • Jenkins 1.569, Delivery Pipeline Plugin 0.8.1, Build Pipeline Plugin 1.4.2/1.4.3,

    Description

      Clicking the icon in the Delivery Pipeline Plugin to run a manual step in a pipeline yields a "Cannot trigger build!" error. Running the manual step in Build Pipeline Plugin is successful (with either 1.4.2 or 1.4.3). Steps to reproduce:

      • Create a pipeline with a manual step
      • Run the pipe up to the manual step
      • Click the icon to the the right of the manual step

      In Chrome, this produces a popup with the error message shown in the attached image.

      Attachments

        Activity

          craftsman Roy Miller created issue -
          jfiser Jeff Fiser added a comment -

          Having the same issue/error on a CENTOS 6.5 server too.

          jfiser Jeff Fiser added a comment - Having the same issue/error on a CENTOS 6.5 server too.

          Delivery Pipeline Plugin 0.8.1 just work with Build Pipeline Plugin 1.4.3.

          Try to reproduce but cant, need some more information:
          Is it just for the fullscreen mode or for both?
          Do you have an Apache or nginx or similar infront of Jenkins?
          Do you see any errors in Jenkins logfile like TriggerException?
          Is Jenkins configured with correct url Jenkins URL in Manage Jenkins > Configure System ?

          patbos Patrik Boström added a comment - Delivery Pipeline Plugin 0.8.1 just work with Build Pipeline Plugin 1.4.3. Try to reproduce but cant, need some more information: Is it just for the fullscreen mode or for both? Do you have an Apache or nginx or similar infront of Jenkins? Do you see any errors in Jenkins logfile like TriggerException? Is Jenkins configured with correct url Jenkins URL in Manage Jenkins > Configure System ?
          craftsman Roy Miller added a comment -

          I can't speak for Jeff, but I see the error in both fullscreen and non-fullscreen. I don't have anything in front of Jenkins, so that's a simplifying factor for me. I didn't see any errors in Jenkins logs either. The Jenkins URL in Manage Jenkins -> Configure System looks right to me.

          craftsman Roy Miller added a comment - I can't speak for Jeff, but I see the error in both fullscreen and non-fullscreen. I don't have anything in front of Jenkins, so that's a simplifying factor for me. I didn't see any errors in Jenkins logs either. The Jenkins URL in Manage Jenkins -> Configure System looks right to me.
          jfiser Jeff Fiser added a comment -

          Hi Patrik,

          Responses to your questions:

          PB - Is it just for the fullscreen mode or for both?
          JF - Yes, errors display for both.

          PB - Do you have an Apache or nginx or similar infront of Jenkins?
          JF - Yes, Apache is running in front of Jenkins

          PB - Do you see any errors in Jenkins logfile like TriggerException?
          JF - No error but I do see a WARNING - WARNING: No valid crumb was included in request for /job/infrastructure/job/rundeck/view/Rundeck%20Resource%20File%20Migration/api/manualStep. Returning 403.

          PB - Is Jenkins configured with correct url Jenkins URL in Manage Jenkins > Configure System ?
          JF - Yes, pointing to the apache URL/Front end.

          jfiser Jeff Fiser added a comment - Hi Patrik, Responses to your questions: PB - Is it just for the fullscreen mode or for both? JF - Yes, errors display for both. PB - Do you have an Apache or nginx or similar infront of Jenkins? JF - Yes, Apache is running in front of Jenkins PB - Do you see any errors in Jenkins logfile like TriggerException? JF - No error but I do see a WARNING - WARNING: No valid crumb was included in request for /job/infrastructure/job/rundeck/view/Rundeck%20Resource%20File%20Migration/api/manualStep. Returning 403. PB - Is Jenkins configured with correct url Jenkins URL in Manage Jenkins > Configure System ? JF - Yes, pointing to the apache URL/Front end.
          patbos Patrik Boström added a comment - - edited

          Thanks for your answers!
          It looks like I can reproduce the issue by enabling "Prevent Cross Site Request Forgery exploits" under Configure Global Security. If enabled I get "Could not trigger build!" if not enabled it will trigger build.

          patbos Patrik Boström added a comment - - edited Thanks for your answers! It looks like I can reproduce the issue by enabling "Prevent Cross Site Request Forgery exploits" under Configure Global Security. If enabled I get "Could not trigger build!" if not enabled it will trigger build.
          patbos Patrik Boström added a comment - - edited Now it will send the crumb needed when "Prevent Cross Site Request Forgery exploits" is enabled. Fixed in commit: https://github.com/Diabol/delivery-pipeline-plugin/commit/ff39674516baed00bf0c071e00ec8324ed6b0b75 https://github.com/Diabol/delivery-pipeline-plugin/commit/913b783ee94f63498d7636136de47c340d0ade66 There is a build containing the fix here: http://build.diabol.se/jenkins/job/Delivery%20Pipeline%20Plugin/job/build/90/se.diabol.jenkins.pipeline$delivery-pipeline-plugin/artifact/se.diabol.jenkins.pipeline/delivery-pipeline-plugin/0.8.2-SNAPSHOT/delivery-pipeline-plugin-0.8.2-SNAPSHOT.hpi Please test it and report back the result. Will be released later this week.
          jfiser Jeff Fiser added a comment -

          You are the man! This fix worked for me.

          Thanks,
          Jeff

          jfiser Jeff Fiser added a comment - You are the man! This fix worked for me. Thanks, Jeff

          Released in 0.8.2

          patbos Patrik Boström added a comment - Released in 0.8.2
          patbos Patrik Boström made changes -
          Field Original Value New Value
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          craftsman Roy Miller added a comment - - edited

          The fix works for me, too. Well done there. The only issue I have now is that the arrows between stages no longer show up, either in FF or Chrome. (I can't seem to attach a screenshot to a ticket comment.)

          My custom stylesheet isn't the problem, because the arrows also don't appear when I'm not using my stylesheet. The same problem exists for fullscreen view and non-fullscreen.

          Did something change when you fixed this ticket that might have broken the arrows?

          craftsman Roy Miller added a comment - - edited The fix works for me, too. Well done there. The only issue I have now is that the arrows between stages no longer show up, either in FF or Chrome. (I can't seem to attach a screenshot to a ticket comment.) My custom stylesheet isn't the problem, because the arrows also don't appear when I'm not using my stylesheet. The same problem exists for fullscreen view and non-fullscreen. Did something change when you fixed this ticket that might have broken the arrows?
          patbos Patrik Boström made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 156370 ] JNJira + In-Review [ 207809 ]

          People

            patbos Patrik Boström
            craftsman Roy Miller
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: