Details
-
Type:
Bug
-
Status: Fixed but Unreleased (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: pipeline-input-step-plugin
-
Labels:None
-
Environment:Jenkins 2.151.0
Pipeline Input Step: 2.9
-
Similar Issues:
Description
I use the following snippet in my DSL pipeline
operators = "ldapUserGroup" ChoiceParameterDefinition choice = new ChoiceParameterDefinition('continue', ['YES'] as String[], 'Description') returnValue = input message: 'DEPLOY ?', parameters: [choice], submitter: operators, submitterParameter: 'approver'
I am not part of the ldapUserGroup thus I would expect the pipeline not to continue. However the pipeline continues anyway.
07:39:05 Approved by Surname Lastname [Pipeline] }
The same happens if i use a particular userID or list of userIDs rather than an ldapGroup
operators = "userID0001,userID0002" ChoiceParameterDefinition choice = new ChoiceParameterDefinition('continue', ['YES'] as String[], 'Description') returnValue = input message: 'DEPLOY ?', parameters: [choice], submitter: operators, submitterParameter: 'approver'
Attachments
Issue Links
- is caused by
-
JENKINS-48998 Can't approve pipeline input step to proceed even when a global admin
-
- In Review
-
- links to
Hi, I've worked around the issue with actually adding cycles into the groovy description of the pipeline. I just wanted to add a note on the fact that for my scenario is not a trust issue, it is more of avoiding potential accidents with production systems. Our admin team can freely adjust the build process too, but we are responsible and don't do that either for the purpose of circumventing protective measures.