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

Input without permissions or not logged in, shows no message

    Details

    • Similar Issues:

      Description

      When adding 'submitter' to an input message to limit the users who can accept the next stage 

      i.e. 

       stage "Pull to the Test Environment"
              input message: 'Ok to proceed?', submitter: 'TeamX'
      

      When trying to proceed as a user without permissions there is no feed back as to why you cannot. 

      Trying to proceed as a user without permission on the overview page produces this error in Chrome Console

      prototype.js:1585 POST http://localhost:8080/job/Testing%20gatling/66/wfapi/inputSubmit?inputId=475c6095275992ca689a7842929d7d8e 500 (Server Error)

      Trying to proceed on the 'Console Log' page produces this error in Chrome Console

      prototype.js:1585 POST http://localhost:8080/job/Testing%20gatling/66/input/475c6095275992ca689a7842929d7d8e/proceedEmpty 400 (Bad Request)

      Going thru to 'Paused for input' on the left hand side (only seems to appear when looking at console log) and clicking proceed without permissions does a full page post and does show some more information.

      NB: You'll have the same problem (no feedback) even if you do not have a submitter if you are not logged in.

        Attachments

          Activity

          Hide
          masond Mason Donahue added a comment -

          I've run into something similar to this as well, when not using a submitter list, when users that have Job.READ but not Job.BUILD click the button. (don't think it matters, but this is a specialized job with a security matrix blocking the default inheritance.) Clicking will cause the 'proceed' button to grey / disable, but when the request 500s, no feedback to the user occurs.

          Weirdly, despite 500-ing, I can't find the error in jenkins's system log, either.

          Jenkins 2.204.1 and pipeline-input-step 2.11.

          I can try creating a simple reproducer case if you'd like, but it will be a bit.

          Show
          masond Mason Donahue added a comment - I've run into something similar to this as well, when not using a submitter list, when users that have Job.READ but not Job.BUILD click the button. (don't think it matters, but this is a specialized job with a security matrix blocking the default inheritance.) Clicking will cause the 'proceed' button to grey / disable, but when the request 500s, no feedback to the user occurs. Weirdly, despite 500-ing, I can't find the error in jenkins's system log, either. Jenkins 2.204.1 and pipeline-input-step 2.11. I can try creating a simple reproducer case if you'd like, but it will be a bit.
          Hide
          sbj Junior Junior added a comment -

          Same issue here, it only works in blue ocean

          Show
          sbj Junior Junior added a comment - Same issue here, it only works in blue ocean
          Hide
          abayer Andrew Bayer added a comment -

          What version of Pipeline: Input Step do you have installed?

          Show
          abayer Andrew Bayer added a comment - What version of Pipeline: Input Step do you have installed?

            People

            • Assignee:
              Unassigned
              Reporter:
              aaronk36 Aaron Knott
            • Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: