| 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. |